https://bugzilla.suse.com/show_bug.cgi?id=1222499 Eugenio Paolantonio changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugenio.paolantonio@suse.co | |m -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222499 https://bugzilla.suse.com/show_bug.cgi?id=1222499#c3 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fcrozat@suse.com) | CC| |luca.dimaio1@gmail.com --- Comment #3 from Frederic Crozat --- Reproducer from Aeon (ie Tumbleweed MicroOS): DBX_CONTAINER_MANAGER="podman" distrobox create --image fedora:latest --name fedora -a "--runtime runc" DBX_CONTAINER_MANAGER="podman" distrobox enter fedora this will fail at "enter" command. However: distrobox rm -f fedora (to do the cleanup) DBX_CONTAINER_MANAGER="podman" distrobox create --image fedora:latest --name fedora -a "--runtime crun" DBX_CONTAINER_MANAGER="podman" distrobox enter fedora will work nicely -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222499 https://bugzilla.suse.com/show_bug.cgi?id=1222499#c5 --- Comment #5 from Luca Di Maio --- After a further investigation, it seems it really is related to that breaking change mounting as ":rslave" something that is :ro, will output that error --- Changing the code for mounting the rootfs into this: for rootdir in /*; do if findmnt --notruncate --noheadings --list --output OPTIONS --target "${rootdir}" | tr ',' '\n' | grep -q "^ro$"; then result_command="${result_command} --volume ${rootdir}:/run/host/${rootdir}:ro,rslave" else result_command="${result_command} --volume ${rootdir}:/run/host/${rootdir}:rslave" fi done Will indeed fix the problem as the different :ro mountpoints are correctly mounted as such: --volume /bin:/run/host/bin:ro,rslave --volume /boot:/run/host/boot:ro,rslave --volume /dev:/run/host/dev:rslave --volume /etc:/run/host/etc:rslave --volume /home:/run/host/home:rslave --volume /lib:/run/host/lib:ro,rslave --volume /lib64:/run/host/lib64:ro,rslave --volume /mnt:/run/host/mnt:ro,rslave --volume /opt:/run/host/opt:rslave --volume /proc:/run/host/proc:rslave --volume /root:/run/host/root:rslave --volume /run:/run/host/run:rslave --volume /sbin:/run/host/sbin:ro,rslave --volume /srv:/run/host/srv:rslave --volume /sys:/run/host/sys:rslave --volume /tmp:/run/host/tmp:rslave --volume /usr:/run/host/usr:ro,rslave --volume /var:/run/host/var:rslave This is a fix that will be added on (my) upstream -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222499 https://bugzilla.suse.com/show_bug.cgi?id=1222499#c7 --- Comment #7 from Luca Di Maio --- Fix has been released https://github.com/89luca89/distrobox/releases/tag/1.7.2.0 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222499 https://bugzilla.suse.com/show_bug.cgi?id=1222499#c9 --- Comment #9 from Aleksa Sarai --- (In reply to Luca Di Maio from comment #5)

After a further investigation, it seems it really is related to that breaking change

mounting as ":rslave" something that is :ro, will output that error

runc treats propagation flags and mount options separately, this is odd. I'll see if I can come up with a test using runc directly (I don't know what podman is doing to the mount options before giving them to runc).

---

Changing the code for mounting the rootfs into this:

for rootdir in /*; do if findmnt --notruncate --noheadings --list --output OPTIONS --target "${rootdir}" | tr ',' '\n' | grep -q "^ro$"; then

result_command="${result_command} --volume ${rootdir}:/run/host/${rootdir}:ro,rslave" else result_command="${result_command} --volume ${rootdir}:/run/host/${rootdir}:rslave" fi done

rro,rslave might be a less painful way of doing this. runc 1.1.0 and later support this though it requires Linux 5.12. -- You are receiving this mail because: You are on the CC list for the bug.