README.BUILD_ERRORS 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. This file lists some common build errors and their solutions.
  2. Error starting remote
  3. ---------------------
  4. If you have an error like this:
  5. ----
  6. Error: Error starting remote:
  7. /bin/sh: 1: adduser: not found
  8. Segmentation fault (core dumped)
  9. ----
  10. You might be having this issue:
  11. https://github.com/docker/docker/issues/28705
  12. When the kernel is configured with CONFIG_LEGACY_VSYSCALL_NONE, running
  13. Debian Wheezy containers fails with a segfault. This should be fixed by
  14. adding "vsyscall=emulate"to the kernel cmdline.
  15. If you are building inside Qubes, you can change the kernel cmdline for
  16. the VM you are using with something like this in dom0:
  17. ----
  18. $ qvm-pref --get [vmname] kernelopts
  19. nopat
  20. $ qvm-pref --set [vmname] kernelopts 'nopat vsyscall=emulate'
  21. ----
  22. If you have an error like this:
  23. ----
  24. Error: Error starting remote:
  25. could not synchronise with container process: no subsystem for mount
  26. ----
  27. You may be experiencing a similar but different problem. Anecdotally
  28. this occured on Ubuntu 18.04 Bionic, kernel 4.15.0-24-generic. You need
  29. to add systemd.legacy_systemd_cgroup_controller=1 to the kernel
  30. boot commandline in /etc/default/grub (followed by `sudo update-grub`).
  31. Error during debootstrap image creation
  32. ---------------------------------------
  33. If the debootstrap-image-.log contains errors similar to the following:
  34. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/zesty/InRelease
  35. Temporary failure resolving 'archive.ubuntu.com'
  36. Check /etc/resolv.conf on the host to see if the nameserver is set to
  37. 127.0.0.1. This can happen when runc performs a bind mount of
  38. /etc/resolv.conf and the host system is running systemd-resolved.
  39. sudo systemctl disable systemd-resolved.service
  40. sudo service systemd-resolved stop
  41. Put the following line in the [main] section of your
  42. /etc/NetworkManager/NetworkManager.conf:
  43. dns=default
  44. Delete the symlink /etc/resolv.conf
  45. rm /etc/resolv.conf
  46. Restart network-manager
  47. sudo service network-manager restart