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!
There's also
a blog linked at the bottom if you want more info.
Best Regards
Scott M
On Mon, May 4, 2020 at 6:29 PM
Matt Heon <mheon@redhat.com> wrote:
On
2020-05-04 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 suggestions?
>
>Ryan
Scott McCarty
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty@redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com
Using Azure Pipelines with Red Hat Universal Base Image and Quay.io: https://red.ht/2TvYo3Y