Rootless podman on Slackware / Dependency on persistence of XDG_RUNTIME_DIR between sessions
by mpeterma from LinuxQuestions.org on (#6KD90)
Hello everyone,
I'm using Slackware 15 as a container runtime for Podman. I'm utilizing Podman with "rootless" containers, meaning processes run from the perspective of a standard user on the host. This setup works great so far, but I have a slight understanding issue.
The Podman command utilizes XDG_RUNTIME_DIR to persist runtime information about running containers. The directory is, for example, /run/user/1000. Here's what I do:
1. SSH login to the host
2. Start a container with Podman: podman start mycontainer
3. List running containers with: podman ps
4. Logout
5. SSH login again
6. List running containers again with: podman ps
As expected, step 3 shows the running containers, but step 6 does not. The cause appears to be that the contents of XDG_RUNTIME_DIR are cleared upon logout. It's worth noting that Slackware uses elogind. Can anyone confirm this and perhaps provide a tip on whether I can change this behavior?
Kind regards
Matthias
I'm using Slackware 15 as a container runtime for Podman. I'm utilizing Podman with "rootless" containers, meaning processes run from the perspective of a standard user on the host. This setup works great so far, but I have a slight understanding issue.
The Podman command utilizes XDG_RUNTIME_DIR to persist runtime information about running containers. The directory is, for example, /run/user/1000. Here's what I do:
1. SSH login to the host
2. Start a container with Podman: podman start mycontainer
3. List running containers with: podman ps
4. Logout
5. SSH login again
6. List running containers again with: podman ps
As expected, step 3 shows the running containers, but step 6 does not. The cause appears to be that the contents of XDG_RUNTIME_DIR are cleared upon logout. It's worth noting that Slackware uses elogind. Can anyone confirm this and perhaps provide a tip on whether I can change this behavior?
Kind regards
Matthias