Closed Dual-0 closed 8 months ago
Looks like the container has been stopped explicitly ?
2023-12-25T10:36:20.924314000Z [supervisor ] SIGTERM received, shutting down...
Looks like the container has been stopped explicitly ?
2023-12-25T10:36:20.924314000Z [supervisor ] SIGTERM received, shutting down...
I haven't done it manually
Do you see anything useful from the host system log ? Somehow the container has been requested to be terminated.
Do you see the problem is you create/start the container yourself ?
@jlesage you are right! The container was stopped automatically from systemd after the user (ansible) logs out.
I found the solution in the podman docs for systemd:
The systemd user instance is killed after the last session for the user is closed. The systemd user instance can be started at boot and kept running even after the user logs out by enabling lingering using
just enable lingering via loginctl enable-linger <username>
Great, thanks for the update !
Current Behavior
When I start the container for the first time via ansible and podman the container restarts after 2 minutes. see 10:36:20
Expected Behavior
The container shouldn't restart after 2 minutes.
Steps To Reproduce
Run Ansible Task:
Environment
Container creation
Container log