Bug#921815: debootstrap umount "host" /proc when running in a Docker container
control: tags -1 -moreinfo Hi Sorry for the late response. I wasn't subscribed to the bug (I assume?). On 23.02.2020 14.01, Hideki Yamane wrote: When running debootstrap inside a Docker container, debootstrap umount both /proc and $TARGET/proc. How do I check it? - run docker - get debootstrap 1.0.110 and install it - debootstrap sid sid - /proc is there inside docker as below Did you use a privileged container? /proc can't be unmounted in a regular non-privileged container. I just tried and "/proc" is unmounted: $ docker run --privileged --rm -t -i debian:stretch-backports bash $ apt-get update && apt-get install -y -t stretch-backports debootstrap $ debootstrap stretch chroot $ ls /proc # it is empty I also tried the debootstrap version in sid: $ docker run --privileged --rm -t -i debian:sid bash $ apt-get update && apt-get install -y debootstrap $ debootstrap sid chroot $ ls /proc # it is empty Also please see the MRs: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/26 https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/27 https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/30 I'm not sure which approach is the best, but Eicke did a short analysis: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/26#note_171042 root@b49ab8b7f3eb:~# ls /proc/ 1 crypto iomemkpageflagspartitions sysrq-trigger 19486 devices ioports loadavg pressure sysvipc acpi diskstatsirq locks sched_debug thread-self asound dma kallsyms meminfo schedstattimer_list buddyinfo driver kcoremisc self tty busexecdomains key-usersmodules slabinfo uptime cgroupsfb keys mountssoftirqs version cmdlinefilesystems kmsg mtrr stat vmallocinfo consoles fs kpagecgroup net swapsvmstat cpuinfointerrupts kpagecount pagetypeinfo sys zoneinfo --- - Kristian Klausen
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
I have opened a MR: https://salsa.debian.org/installer-team/debootstrap/merge_requests/26
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
Package: debootstrap Version: 1.0.110~bpo9+1 Hi When running debootstrap inside a Docker container, debootstrap umount both /proc and $TARGET/proc. This is due to a missing check at: https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L104 Due to the missing check debootstrap umount "$TARGET/proc", which is a symlink to /proc [1]. I will open a MR shortly. [1] https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L68 - Kristian Klausen
Bug#818065: Sv: Bug#818065: console-setup is not read correctly at boottime and must be started manually
Hello Anton > Yes, in this case setupcon is never run from console-setup.sh. However > there is no need to use setupcon in order to configure the font because > this is done by /lib/udev/rules.d/90-console-setup.rules and the > keyboard is configured by /lib/systemd/system/keyboard-setup.service. keyboard-setup.service doesn't seems to configure the layout, rerunning it change nothing but as soon I rerun console-setup.service the layout is fixed. > How big is is this image? Will it be possible to send it to me so I can > test? Around ~ 700MB, but I need to strip a few thing out before I can share it. I'm properly just gonna upload it to my webserver. Regards Kristian Klausen
Bug#818065: console-setup is not read correctly at boottime and must be started manually
Hello I have just experienced this issue after "upgrading" (rebuilding) my live image to stretch from jessie. As it is a live-image, every boot is "first boot" as Anton said could give issue. So I looked a bit on the code, and I think the issue is caused by line 11 in console-setup (*), the line make so console-setup.sh does nothing at first run after boot, and as console-setup.service is only run once per boot, setupcon (which configure keyboard layout) is never run. How did this ever get into testing? :) * https://anonscm.debian.org/cgit/d-i/console-setup.git/tree/init/console-setup.sh?id=85d541bcfe7557caee0e544ac6c547f97174db32#n11 Regards Kristian Klausen
