Bug#921815: Extra information about /proc

Hello Thorsten, On 27/11/2023 05:58, Thorsten Glaser wrote: reopen 921815 thanks But did you also test whether /proc was not umounted? Before and after the debootstrap command, the output of mount inside the docker container is identical. Then I exit the docker container, and in the host

Bug#921815: Works in buster

reopen 921815 thanks On Wed, 8 Nov 2023, Roland Clobus wrote: > While triaging #919659, I found this bug report. […] > It works, debootstrap reports: > I: Base system installed successfully. But did you also test whether /proc was not umounted? bye, //mirabilos -- Infrastrukturexperte • Qvest

Processed: Re: Works in buster

Processing commands for cont...@bugs.debian.org: > reopen 921815 Bug #921815 {Done: Roland Clobus } [debootstrap] debootstrap umount "host" /proc when running in a Docker container 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and

weird interaction (bug?) between two-stage debootstrap and dpkg-divert

Hi, I ran into this because I have an elaborate chroot script¹ that handles start-stop-daemon, initctl, policy-rc.d, etc. and can reproduce this as follows: I’ve debootstrapped bullseye up to first stage, then entered the chroot and: # dpkg-divert --local --quiet --rename --divert