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

[Thorsten Glaser <tg@mirbsd.de>]

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