Hi Sage, that is an issue with Podman that is already fixed upstream and the fix is in 1.7. Now we don't set XDG_RUNTIME_DIR for the root user. Giuseppe Sage Weil <sweil@redhat.com> writes:
Hi,
On my fedora 31 box, podman + crun are putting state in /run/user/0/crun. This is fine until I ssh into the box as root and then log out, at which point systemd blows away all of /run/user/0, and podman half-breaks (can't podman exec, podman kill on containers fails to stop conmon, etc.).
I'm not sure why it's using /run/user/0/crun instead of /run/crun, though, since I'm starting the containers as UID 0. It looks like the conmon process as the XDG_RUNTIME_DIR=/run/user/0 set in its environment. Why does libpod set that, though, when the user is root? Using /run/user/0 seems like a fundamentally broken strategy, since that is an ephemeral directory that systemd will blow away when the user logs out...
FWIW I'm running
podman-1.6.2-2.fc31.x86_64 crun-0.10.6-1.fc31.x86_64
Thanks! sage _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io