Public bug reported: Running `yes | pbuilder-dist stonking arm64 create --updates-only` prints a bunch of normal logs, but then ends with an error.
This turns out to be because the chroot is sanity checked with /bin/true, which in the rust coreutils is a multi use executable that checks its exec path name to see what it should do. However in a debootstrap+docker environment /proc/self/exe is a symlink pointing to itself, causing the loop. This wasn’t a problem before with the old coreutils because /bin/true didn’t try to read procfs. There exists an env var you can set to tell the debootstrap environment it is in a container (it is imaginatively named container) and if you set it to lxc instead of docker then the procfs is properly mounted into the environment instead of symlinked to itself. relevant extract from logs: W: Failure trying to run: chroot "/var/cache/pbuilder/build/310" /bin/true W: See /var/cache/pbuilder/build/310/debootstrap/debootstrap.log for details E: debootstrap failed thread 'main' (4829) panicked at src/bin/coreutils.rs:81:13: Unable to read /proc/self/exe: Too many levels of symbolic links (os error 40) note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Aborted (core dumped) E: End of debootstrap.log W: Aborting with an error Thread where it was suggested that I file this bug, so that I don't get told I shouldn't have done so: https://discourse.ubuntu.com/t/pbuilder- dist-cannot-create-a-26-10-chroot/87034 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2166212 Title: Pbuilder-dist cannot create a 26.10 chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2166212/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
