Bug#953637: debootstrap remove /proc when ran under docker
Package: debootstrap
Version: 1.0.114
On a fresh install buster under docker I ran "debootstrap buster test".
This lead to a system without /proc mounted.
The following error are found:
>> I: Target architecture can be executed
>> I: Retrieving InRelease
>> I: Checking Release signature
>> I: Valid Release signature (key id 6D33866EDD8FFA41C0143AEDDCC9EFBF77E11517)
>> I: Retrieving Packages
>> I: Validating Packages
>> I: Resolving dependencies of required packages...
>> I: Resolving dependencies of base packages...
>> I: Checking component main on http://deb.debian.org/debian...
>> I: Validating libacl1 2.2.53-4
>> I: Validating adduser 3.118
>> I: Validating apt 1.8.2
[...]
>> I: Extracting mount...
>> I: Extracting util-linux...
>> I: Extracting liblzma5...
>> I: Extracting zlib1g...
>> W: Failure trying to run: chroot "//test" mount -t proc proc /proc
>> W: See //test/debootstrap/debootstrap.log for details
>> I: Installing core packages...
>> I: Unpacking required packages...
>> I: Unpacking libacl1:amd64...
>> I: Unpacking adduser...
[...]
In the debootstrap.log I saw:
mount: /proc: mount(2) system call failed: Too many levels of symbolic links.
It reproduces always, even with different host OS (stretch and gentoo are tested)
I have also tried the "testing" version without changes.
Reply to: