I saw that they updated the troubleshooting documentation. I had trouble finding it via google so the more places this different is documented is good for future googlers. Perhaps a warning could be displayed when running "podman run -d " as user and linger is not enabled?
This seems to be a fairly common
failure for users. Is there anything we could do in
`podman generate systemd` to point out
the problem to users? IE in the generated unit files, if we
pointed to the linger command there in a comment? Would this have
On 5/11/20 09:37, Ryan Wilson wrote:
Thanks so much for the quick help with this last
week. I finally got to test it and yes, this indeed was the
problem. "loginctl enable-linger" fixed it. I didn't know
systemd was doing this. I guess the KillUserProcesses features
is turned off by default in my desktop distribution. Thanks for
pointing out the problem!
18:10, Ryan Wilson wrote:
>Hi podman team,
>I wanted to try out Fedora CoreOS for a couple of
upcoming projects so I
>installed it on bare metal and logged in via ssh.
I can start a container
>detached (as my logged in user) and then verify
that the server is running
>but when I logout of the ssh session, the
container stops. From looking at
>the logs, it appears that the container process is
getting SIGTERM Which I
>assume means the container was stopped gracefully.
But by what? How do I
>stop this behavior? If I detach a container, I
would like it to outlive my
>session. This doesn’t happen when I sudo to root
and start the container,
>only when running as the non-root user. Any