Issues with linux-user-chroot (eg "too many mounts")
Created by: gtristan
Today I wiped my cache to start to rebuild from scratch.
Using linux-user-chroot, at first I hit the "too many mounts" bug, however I already had the fixed package which sets the arbitrary maximum at 1024.
After manually hacking the linux-user-chroot sources to use a limit of 2048, I was able to build stage1-binutils, however during the artifact creation; ybd consistently failed to cleanup the directory with a "Device or resource busy" error.
Uninstalling linux-user-chroot fixes this issue by falling back on regular mounts.
This is most probably an issue with upstream linux-user-chroot. We should probably have an option or environment variable to allow ignoring an installed linux-user-chroot until we can vouch for it's reliability.