Debian Bug report logs - #930684
pbuilder: creation of build env fails when run inside Docker container

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Tobias Junghans <tobydox@veyon.io>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: pbuilder: creation of build env fails when run inside Docker container

Date: Tue, 18 Jun 2019 13:49:27 +0000

Package: pbuilder
Version: 0.230.4
Severity: important
Tags: upstream

Hi,

I tried to upgrade my Docker-based pbuilder containers from stretch to
buster. However it appears that pbuilder and/or debootstrap do not work
properly inside Docker containers any longer due to issues with mounting
special filesystems such as proc and devpts.

The issue can be reproduced easily in a Debian Buster based container:

# docker run --privileged -it debian:buster /bin/bash

root@d81f634fe4a0:/# cat /proc/mounts
overlay / overlay rw,relatime,lowerdir=/var/lib/docker/overlay2/l/TPOD4JNRBNCTMXNHYCY5XVRBQ3:/var/lib/docker/overlay2/l/TSD62UVCIJQ2LJ4XTUHKTVEK77,upperdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/diff,workdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/work 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,size=65536k,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
/dev/sdb /etc/resolv.conf ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
/dev/sdb /etc/hostname ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
/dev/sdb /etc/hosts ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0

root@d81f634fe4a0:/# apt-get update && apt-get -y --no-install-recommends install pbuilder

[...]

root@d81f634fe4a0:/# pbuilder create --distribution buster
W: /root/.pbuilderrc does not exist
W: cgroups are not available on the host, not using them.
I: Distribution is buster.
I: Current time: Tue Jun 18 13:27:34 UTC 2019
I: pbuilder-time-stamp: 1560864454
I: Building the build environment
I: running debootstrap
/usr/sbin/debootstrap
I: Retrieving InRelease 
I: Checking Release signature
I: Valid Release signature (key id 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC)
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: Retrieving libacl1 2.2.53-4
I: Validating libacl1 2.2.53-4

[...]

W: Failure trying to run: chroot "/var/cache/pbuilder/build/489" mount -t proc proc /proc
W: See /var/cache/pbuilder/build/489/debootstrap/debootstrap.log for details

[...]

Setting up aptitude (0.8.11-7) ...
update-alternatives: using /usr/bin/aptitude-curses to provide /usr/bin/aptitude (aptitude) in auto mode
Processing triggers for libc-bin (2.28-10) ...
I: Copying back the cached apt archive contents
I: new cache content 'aptitude-common_0.8.11-7_all.deb' added
I: new cache content 'libboost-iostreams1.67.0_1.67.0-13_amd64.deb' added
I: new cache content 'aptitude_0.8.11-7_amd64.deb' added
I: new cache content 'libsqlite3-0_3.27.2-3_amd64.deb' added
I: new cache content 'libxapian30_1.4.11-1_amd64.deb' added
I: new cache content 'libcwidget3v5_0.5.17-11_amd64.deb' added
I: new cache content 'libboost-system1.67.0_1.67.0-13_amd64.deb' added
I: new cache content 'libsigc++-2.0-0v5_2.10.1-2_amd64.deb' added
mount: failed to read mtab: No such file or directory
mount: failed to read mtab: No such file or directory
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: creating base tarball [/var/cache/pbuilder/base.tgz]
mount: failed to read mtab: No such file or directory
I: cleaning the build env 
I: removing directory /var/cache/pbuilder/build/489 and its subdirectories
rm: cannot remove '/var/cache/pbuilder/build/489/dev/ptmx': Device or resource busy
mount: failed to read mtab: No such file or directory
I: cleaning the build env 
I: removing directory /var/cache/pbuilder/build/489 and its subdirectories
rm: cannot remove '/var/cache/pbuilder/build/489/dev/ptmx': Device or resource busy
rmdir: failed to remove '/var/cache/pbuilder/build/489/dev': Directory not empty
rmdir: failed to remove '/var/cache/pbuilder/build/489': Directory not empty

root@d81f634fe4a0:/# cat /proc/mounts
cat: /proc/mounts: No such file or directory

root@d81f634fe4a0:/# mount proc /proc -t proc
root@d81f634fe4a0:/# cat /proc/mounts
overlay / overlay rw,relatime,lowerdir=/var/lib/docker/overlay2/l/TPOD4JNRBNCTMXNHYCY5XVRBQ3:/var/lib/docker/overlay2/l/TSD62UVCIJQ2LJ4XTUHKTVEK77,upperdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/diff,workdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/work 0 0
tmpfs /dev tmpfs rw,nosuid,size=65536k,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
/dev/sdb /etc/resolv.conf ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
/dev/sdb /etc/hostname ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
/dev/sdb /etc/hosts ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
devpts /var/cache/pbuilder/build/489/dev/ptmx devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
proc /proc proc rw,relatime 0 0


debootstrap.log contains the following message regarding the proc mount

mount: /proc: mount(2) system call failed: Too many levels of symbolic links.

Thank you for looking into this issue. Until then I'll continue to use
the stretch-based pbuilder container and use it to build packages for buster.

Best regards

Tobias

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.1.2 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  debootstrap            1.0.114
ii  dpkg-dev               1.19.7

Versions of packages pbuilder recommends:
pn  devscripts  <none>
pn  eatmydata   <none>
pn  fakeroot    <none>
ii  iproute2    4.20.0-2
pn  sudo        <none>

Versions of packages pbuilder suggests:
pn  cowdancer   <none>
pn  gdebi-core  <none>

Message #8 received at 930684@bugs.debian.org (full text, mbox, reply):

From: Mattia Rizzolo <mattia@debian.org>

To: Tobias Junghans <tobydox@veyon.io>, 930684@bugs.debian.org

Subject: Re: Bug#930684: pbuilder: creation of build env fails when run inside Docker container

Date: Tue, 18 Jun 2019 18:29:51 +0200

[Message part 1 (text/plain, inline)]

Control: reassign -1 debootstrap 1.0.114
Control: tag -1 - upstream

On Tue, Jun 18, 2019 at 01:49:27PM +0000, Tobias Junghans wrote:
> I tried to upgrade my Docker-based pbuilder containers from stretch to
> buster. However it appears that pbuilder and/or debootstrap do not work
> properly inside Docker containers any longer due to issues with mounting
> special filesystems such as proc and devpts.

From your log it seems like it's debootstrap that is actually failing.

I don't use docker and I don't really want to figure out how to try it,
so I'll just bounce the ball to the debootstrap maintainers :)

> The issue can be reproduced easily in a Debian Buster based container:
> 
> # docker run --privileged -it debian:buster /bin/bash
> 
> root@d81f634fe4a0:/# cat /proc/mounts
> overlay / overlay rw,relatime,lowerdir=/var/lib/docker/overlay2/l/TPOD4JNRBNCTMXNHYCY5XVRBQ3:/var/lib/docker/overlay2/l/TSD62UVCIJQ2LJ4XTUHKTVEK77,upperdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/diff,workdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/work 0 0
> proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> tmpfs /dev tmpfs rw,nosuid,size=65536k,mode=755 0 0
> devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
> cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
> cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
> cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
> cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
> cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
> cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
> cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
> cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
> cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
> cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
> mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
> /dev/sdb /etc/resolv.conf ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> /dev/sdb /etc/hostname ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> /dev/sdb /etc/hosts ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
> devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> 
> root@d81f634fe4a0:/# apt-get update && apt-get -y --no-install-recommends install pbuilder
> 
> [...]
> 
> root@d81f634fe4a0:/# pbuilder create --distribution buster
> W: /root/.pbuilderrc does not exist
> W: cgroups are not available on the host, not using them.
> I: Distribution is buster.
> I: Current time: Tue Jun 18 13:27:34 UTC 2019
> I: pbuilder-time-stamp: 1560864454
> I: Building the build environment
> I: running debootstrap
> /usr/sbin/debootstrap
> I: Retrieving InRelease 
> I: Checking Release signature
> I: Valid Release signature (key id 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC)
> 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: Retrieving libacl1 2.2.53-4
> I: Validating libacl1 2.2.53-4
> 
> [...]
> 
> W: Failure trying to run: chroot "/var/cache/pbuilder/build/489" mount -t proc proc /proc
> W: See /var/cache/pbuilder/build/489/debootstrap/debootstrap.log for details
> 
> [...]
> 
> Setting up aptitude (0.8.11-7) ...
> update-alternatives: using /usr/bin/aptitude-curses to provide /usr/bin/aptitude (aptitude) in auto mode
> Processing triggers for libc-bin (2.28-10) ...
> I: Copying back the cached apt archive contents
> I: new cache content 'aptitude-common_0.8.11-7_all.deb' added
> I: new cache content 'libboost-iostreams1.67.0_1.67.0-13_amd64.deb' added
> I: new cache content 'aptitude_0.8.11-7_amd64.deb' added
> I: new cache content 'libsqlite3-0_3.27.2-3_amd64.deb' added
> I: new cache content 'libxapian30_1.4.11-1_amd64.deb' added
> I: new cache content 'libcwidget3v5_0.5.17-11_amd64.deb' added
> I: new cache content 'libboost-system1.67.0_1.67.0-13_amd64.deb' added
> I: new cache content 'libsigc++-2.0-0v5_2.10.1-2_amd64.deb' added
> mount: failed to read mtab: No such file or directory
> mount: failed to read mtab: No such file or directory
> I: unmounting dev/pts filesystem
> I: unmounting dev/shm filesystem
> I: unmounting proc filesystem
> I: unmounting sys filesystem
> I: creating base tarball [/var/cache/pbuilder/base.tgz]
> mount: failed to read mtab: No such file or directory
> I: cleaning the build env 
> I: removing directory /var/cache/pbuilder/build/489 and its subdirectories
> rm: cannot remove '/var/cache/pbuilder/build/489/dev/ptmx': Device or resource busy
> mount: failed to read mtab: No such file or directory
> I: cleaning the build env 
> I: removing directory /var/cache/pbuilder/build/489 and its subdirectories
> rm: cannot remove '/var/cache/pbuilder/build/489/dev/ptmx': Device or resource busy
> rmdir: failed to remove '/var/cache/pbuilder/build/489/dev': Directory not empty
> rmdir: failed to remove '/var/cache/pbuilder/build/489': Directory not empty
> 
> root@d81f634fe4a0:/# cat /proc/mounts
> cat: /proc/mounts: No such file or directory
> 
> root@d81f634fe4a0:/# mount proc /proc -t proc
> root@d81f634fe4a0:/# cat /proc/mounts
> overlay / overlay rw,relatime,lowerdir=/var/lib/docker/overlay2/l/TPOD4JNRBNCTMXNHYCY5XVRBQ3:/var/lib/docker/overlay2/l/TSD62UVCIJQ2LJ4XTUHKTVEK77,upperdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/diff,workdir=/var/lib/docker/overlay2/aa29cac2d0ebecfb12fdd71a9952845140052615f2bd746c4336daa8d7a4d533/work 0 0
> tmpfs /dev tmpfs rw,nosuid,size=65536k,mode=755 0 0
> devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
> cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
> cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
> cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
> cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
> cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
> cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
> cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
> cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
> cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
> cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
> mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
> /dev/sdb /etc/resolv.conf ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> /dev/sdb /etc/hostname ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> /dev/sdb /etc/hosts ext4 rw,noatime,nodiratime,commit=300,data=ordered 0 0
> shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0
> devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> devpts /var/cache/pbuilder/build/489/dev/ptmx devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0
> proc /proc proc rw,relatime 0 0
> 
> 
> debootstrap.log contains the following message regarding the proc mount
> 
> mount: /proc: mount(2) system call failed: Too many levels of symbolic links.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[signature.asc (application/pgp-signature, inline)]

Message #21 received at 930684@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <tg@mirbsd.de>

To: Tobias Junghans <tobydox@veyon.io>, 930684@bugs.debian.org

Subject: Re: Bug#930684: pbuilder: creation of build env fails when run inside Docker container

Date: Tue, 18 Jun 2019 19:10:53 +0000 (UTC)

Tobias Junghans dixit:

>I tried to upgrade my Docker-based pbuilder containers from stretch to

Erm… why do you use chroots inside of chroots? That’s… tricky.

>mount: failed to read mtab: No such file or directory

This might be a container issue.

>mount: /proc: mount(2) system call failed: Too many levels of symbolic links.

Check if /proc outside of pbuilder but inside the container is right.

There also might be a /dev/shm vs. /run/shm issue. I recently had a
failure with these (one’s a mountpoint, the other a symbolic link to
it, either way works but it’s got to be consistent inside and out‐
side of the chroot) with schroot.

>the stretch-based pbuilder container and use it to build packages for buster.

Don’t.

But with {cow|p}builder --login --save-after-login you can
upgrade the base to buster inside pbuilder.

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

Message #26 received at 930684@bugs.debian.org (full text, mbox, reply):

From: Tobias Junghans <tobydox@veyon.io>

To: Thorsten Glaser <tg@mirbsd.de>

Cc: Tobias Junghans <tobydox@veyon.io>, 930684@bugs.debian.org

Subject: Re: Bug#930684: pbuilder: creation of build env fails when run inside Docker container

Date: Wed, 19 Jun 2019 09:02:10 +0200

Am Dienstag, 18. Juni 2019, 21:10:53 CEST schrieb Thorsten Glaser:
> Tobias Junghans dixit:
> >I tried to upgrade my Docker-based pbuilder containers from stretch to
> 
> Erm… why do you use chroots inside of chroots? That’s… tricky.

Simple because we use Gitlab Runners with the builtin Docker Executor 
(https://docs.gitlab.com/runner/executors/docker.html) for running all kinds 
of jobs in a generic manner. Depending on the project individual pre-built 
Docker images (specified in the CI config) providing the desired build tools 
and toolchains are used. The jobs for building Debian packages use a Docker 
container with Debian and pbuilder installed.

This used to work for years but for Buster-based containers (i.e. pbuilder and 
debootstrap from Buster) it doesn't any longer.


> >mount: failed to read mtab: No such file or directory
> 
> This might be a container issue.

The mounts are fine before running pbuilder/debootstrap. Afterwards proc is 
not mounted even in the Docker container. The state of the container and its 
mounts shouldn't change when running debootstrap. I also saw Docker/container-
related changes between 1.0.89 (stretch) and buster (1.0.114) which likely 
cause the misbehaviour:

https://salsa.debian.org/installer-team/debootstrap/commit/
5a0f16664066b24c42c074643a4ca178890d7af7
https://salsa.debian.org/installer-team/debootstrap/commit/
0962af1527a1ba0e996a0b442b159b4dbf164988
https://salsa.debian.org/installer-team/debootstrap/commit/
1e7549c57c0f15816c89c4f243051785ca383be9

> >mount: /proc: mount(2) system call failed: Too many levels of symbolic
> >links.
> Check if /proc outside of pbuilder but inside the container is right.

/proc in the container is fine, see first output of "cat /proc/mounts
" in by original bug report.
 
> But with {cow|p}builder --login --save-after-login you can
> upgrade the base to buster inside pbuilder.

It's not about the pbuilder environment itself but the Docker container used 
for invoking pbuilder/debootstrap. Using a stretch-based Docker container and 
debootstrapping Buster works fine.

Thanks and best regards

Tobias

Message #31 received at 930684@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <tg@mirbsd.de>

To: Tobias Junghans <tobydox@veyon.io>

Cc: 930684@bugs.debian.org

Subject: Re: Bug#930684: pbuilder: creation of build env fails when run inside Docker container

Date: Wed, 19 Jun 2019 13:34:06 +0000 (UTC)

Tobias Junghans dixit:

>> But with {cow|p}builder --login --save-after-login you can
>> upgrade the base to buster inside pbuilder.
>
>It's not about the pbuilder environment itself but the Docker container used 
>for invoking pbuilder/debootstrap. Using a stretch-based Docker container and 
>debootstrapping Buster works fine.

Ah okay. Yes, that’s supported, a difference of only one version,
as long as the host has (at least) the stretch kernel.

As for the other things, the debootstrap people might look at it.

bye,
//mirabilos
-- 
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

Message #36 received at 930684@bugs.debian.org (full text, mbox, reply):

From: Steven Shiau <steven@nchc.org.tw>

To: 930684@bugs.debian.org

Subject: [Patch] Make /proc won't be unmounted in docker instance

Date: Sun, 8 Mar 2020 22:20:49 +0800

[Message part 1 (text/plain, inline)]

Dear maintainer,

Attached please find the patch file to address this bug.
In /usr/share/debootstrap/scripts/debian-common,
The function first_stage_install () {
...
       if doing_variant fakechroot || [ "$CONTAINER" = "docker" ]; then
                setup_proc_symlink
       fi

which will make the chroot's /proc in docker instance link the host's /proc.
Hence in the function "setup_proc" in /usr/share/debootstrap/functions,
this line:
                umount "$TARGET/proc" 2>/dev/null || true
will unmount the docker instance's /proc, and it causes this issue.

I believe you definitely have a better solution for this, but the patch
for debootstrap 1.0.120 works for me.
My 2 cents.

Steven

-- 
Steven Shiau <steven _at_ stevenshiau org>
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5  356C 8E94 C9CD 163E 3FB0

[functions.diff (text/x-patch, attachment)]

Message #45 received at 968927-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 968927-close@bugs.debian.org

Subject: Bug#968927: fixed in debootstrap 1.0.124

Date: Mon, 26 Apr 2021 14:18:57 +0000

Source: debootstrap
Source-Version: 1.0.124
Done: Dimitri John Ledkov <xnox@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968927@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dimitri John Ledkov <xnox@ubuntu.com> (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 26 Apr 2021 15:02:44 +0100
Source: debootstrap
Architecture: source
Version: 1.0.124
Distribution: experimental
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Dimitri John Ledkov <xnox@ubuntu.com>
Closes: 968927
Launchpad-Bugs-Fixed: 1923845
Changes:
 debootstrap (1.0.124) experimental; urgency=medium
 .
   [ Colin Watson ]
   * Add (Ubuntu) groovy as a symlink to gutsy.
 .
   [ Samuel Thibault ]
   * functions: Turn for loops variables into locals, suggested by jhcha54008.
 .
   [ YunQiang Su ]
   * stage1: re-mkdir /proc if it is a symlink instead of umount. (Closes: #968927)
 .
   [ Luca Falavigna ]
   * Add (Ubuntu) hirsute as a symlink to gutsy.
 .
   [ Tobias Koch ]
   * Add --inrelease-path option to allow specifying by-hash InRelease
     location.
 .
   [ Dimitri John Ledkov ]
   * functions: add zstd control&data support to the ar extractor LP: #1923845
   * Add (Ubuntu) impish as a symlink to gutsy.
   * gutsy: sync changes from Ubuntu, to ensure that impish+ are always
     merged-usr.
   * gutsy: use --extractor=ar if dpkg-deb has no zstd support (i.e. on
     Debian & non-Ubuntu derivatives).
   * rules,control: adjust Recommends/Suggests to be appropriate on each
     distro.
Checksums-Sha1:
 ba383bd966469131c6781698635eb9509544a26a 1919 debootstrap_1.0.124.dsc
 204a1a7f742c2772fe2ca0139da948cf95787750 78498 debootstrap_1.0.124.tar.gz
 25f26e92a1b7b8dd89f7c38789b2594721010e20 7982 debootstrap_1.0.124_source.buildinfo
Checksums-Sha256:
 8b0a5c2ef1935e2cbd7e8f259041a29e33f12eba5314d53a209e9847963b043f 1919 debootstrap_1.0.124.dsc
 7700e9864b29f166b26c54153ed8c275b46f4b9a60468bb607e019a64c16cd8f 78498 debootstrap_1.0.124.tar.gz
 4f5fe6ca3b0572d4b22eaa879902e9f84e4ae4f41ca2a134e64ea28b680a6f02 7982 debootstrap_1.0.124_source.buildinfo
Files:
 95a8ee2918ccd1fc3bae1a4af3f0b0a7 1919 admin optional debootstrap_1.0.124.dsc
 8a5e97f60236c3a63f715c056a5f0e29 78498 admin optional debootstrap_1.0.124.tar.gz
 78fe5582636a1b4296758391d7dad7c6 7982 admin optional debootstrap_1.0.124_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAmCGyCYACgkQm47ISdXv
cO3kbRAAioQ3jz3p8wZrYOWcVH8kBOfK231/DSFfB+hpJoYhF/B0jD2pCI+7qgNJ
zwAkHRGb6V8mJPg/vZ00320Nu4axQoaLLiE+Y9Dy74tLxVFVZVEqnB07Kb2/9BDv
y2eqWgNqPF9vAstdt0YjZEGxdaBq7jgHnKyGJl0FCuLnWA+Ev7F2s65S8B8RqH6t
5a/T5q52qM2z/4WCxwIJELsth4vtScNUuLqMacMRgR+lPSB6aRX0IbuiASuHO8qV
jFGFCgJEU7H6nzzr1qsCzCG7jlhWsFlVu3ibMutf4O1nfnDwka9/tVlCbvwu8vtE
RLtTYYWy67fa6d7zt1VCVsFaJO+5bhhoj7MAo8MiBeTfjYqMG0sAcuS0YzEdu5JN
/xqk5DAvb/LNDerkNTJbiCDMo3W6NLgZS6Mjpb2OeJ7rHpDChBOD9TzdP/+9WW28
Sbg0x1tpUt267EoVU1I63TaqUrj3iJFNb18pI63xbVVkB4H5TJM06Ah0oz5HTcN7
FcMUpxslfQ9nIrQOb9o93NdKFM+UR/6JNuiEucpQhLBsv9wdLgsrcqHkrRASJg+S
BGMEAPp+4Vhi+V3UoP07DruXL71ZT3TgAbSdEnsBd8HpEcYc20wd9RK9Atk7+8sf
FFe1QtvUGgNmfHiNJYdiCfyIxbeT3EpfUpCVsqEQAoWiy2rJ+Ek=
=ZiXm
-----END PGP SIGNATURE-----

Message #46 received at 968927-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 968927-close@bugs.debian.org

Subject: Bug#968927: fixed in debootstrap 1.0.125

Date: Tue, 02 Nov 2021 11:33:43 +0000

Source: debootstrap
Source-Version: 1.0.125
Done: Samuel Thibault <sthibault@debian.org>

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968927@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 19 Aug 2021 13:49:19 +0200
Source: debootstrap
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0.125
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Samuel Thibault <sthibault@debian.org>
Closes: 968927 985481 985811
Launchpad-Bugs-Fixed: 1923845
Changes:
 debootstrap (1.0.125) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * functions (download_main): Let the loops try the different components and
     suites when the checksum doesn't match. This is needed when several of
     them contain the same package name.
 .
   [ Arnaud Rebillout ]
   * Fix auto proxy discovery (Closes: #985811)
   * Fix detection of docker container for cgroup v2 (Closes: #985481)
 .
   [ Johannes 'josch' Schauer ]
   * functions: define link_dir before using it.
 .
   [ Hideki Yamane ]
   * Add (Debian) trixie as a symlink to sid.
 .
   [ Dimitri John Ledkov ]
   * Add (Ubuntu) jammy as a symlink to gutsy.
   * Upload to unstable.
 .
 debootstrap (1.0.124) experimental; urgency=medium
 .
   [ Colin Watson ]
   * Add (Ubuntu) groovy as a symlink to gutsy.
 .
   [ Samuel Thibault ]
   * functions: Turn for loops variables into locals, suggested by jhcha54008.
 .
   [ YunQiang Su ]
   * stage1: re-mkdir /proc if it is a symlink instead of umount. (Closes: #968927)
 .
   [ Luca Falavigna ]
   * Add (Ubuntu) hirsute as a symlink to gutsy.
 .
   [ Tobias Koch ]
   * Add --inrelease-path option to allow specifying by-hash InRelease
     location.
 .
   [ Dimitri John Ledkov ]
   * functions: add zstd control&data support to the ar extractor LP: #1923845
   * Add (Ubuntu) impish as a symlink to gutsy.
   * gutsy: sync changes from Ubuntu, to ensure that impish+ are always
     merged-usr.
   * gutsy: use --extractor=ar if dpkg-deb has no zstd support (i.e. on
     Debian & non-Ubuntu derivatives).
   * rules,control: adjust Recommends/Suggests to be appropriate on each
     distro.
Checksums-Sha1:
 2e2f3de1cb47a1477754be43e54b8e13b7c3796e 1919 debootstrap_1.0.125.dsc
 1a6e5ea0743cafd8814b3921d6086f526b0b2c34 78777 debootstrap_1.0.125.tar.gz
 1f3fe6472f80c4c97c61072d5e665010367a9b02 8649 debootstrap_1.0.125_source.buildinfo
Checksums-Sha256:
 87ccaf0676817f7c193ed48ee68018b8898ecb7b05f7727549e40f64d73fac22 1919 debootstrap_1.0.125.dsc
 9c4c7ca8f3f6653e7eca65aae77bbf7f723d7395fb48403bbc2256ce8b24ec1a 78777 debootstrap_1.0.125.tar.gz
 03b0b8cad8cb9fd527400a8488e5c18c14e6d331d76c760dd64d33bc9a1e236c 8649 debootstrap_1.0.125_source.buildinfo
Files:
 96291c94bbb8c27237d63b36a3d20141 1919 admin optional debootstrap_1.0.125.dsc
 e18f10e1952f6622aa027a7e8d980935 78777 admin optional debootstrap_1.0.125.tar.gz
 e670578e531a636d61fcfec598e0f8eb 8649 admin optional debootstrap_1.0.125_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAmGBHL8ACgkQm47ISdXv
cO0/iw/8Db2QzJlaEvYluWpVge4IejT5jtnQLTaPsMkQAeP6wC+GRJ0Dy7sAXtEU
qCHVoFBzf+a/c4fJsF11AidRAop1CU6pa9XLky2tnlzgEmURvqsgL8bPEx7UuygO
yjHzNyXK+9n3ku3qbYy5jfoElllg+7kSLzBEPC5Bw3P/dAoEMRf7x2T6iPV9QNCO
OxgBQNUHTNvkfX9fvNq+6CqrjhLrKNmRqjbHzELJhAXQavs6RBSXCG8O+EbD0eYJ
FvMF1kELymk5gxoMv8McgwMEaKYNaaVRQOaDHa4OlJRQ0ic30m1kPAUO0yc3uZUn
eBmm7BfXBxxVBMYVGvcGzwmZyRQ3g+ArQ3x7hf59OcvFuCKnhxWPrK6IEBL64S4y
G/bAn71s/qqYTSTV8MDY2AXrYbPdMUQzEa5KJS/iSfotUClaBZmmfNrAiQt5JIC9
1htxBT3vyOUKHUxGH1SRTNDyBfnimEQep4mGkIu4rZLcFfL9aZSpVN930DAIuXAk
1+3rzpcZoZ3wvSk+/9PB4vA4gZ7c3ZuttSVbVlJa/SdDSAkg3jgmDQCIP+up9Syr
OkDXX8kHE1pEH8V0rdsVt/wV4xnqs0W5kX7WxVpI6Teqzyi918kNzeam/n0ovE0A
H3LH2yeRqsUQDJB1J1d3W/7ugQltrmhDnH71yPKbs+czV7XQGfE=
=+ZHG
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.