You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your use-case which is not covered by existing documentation.
I'm running Jenkins in Podman (not my choice), and the auto-restart policy described here https://www.jenkins.io/blog/2022/05/27/docker-image-new-lifecycle/ doesn't work. I'm sure it's an issue with Podman and not Jenkins, but I still have to manually reset the Jenkins controller container whenever updating plugins or any other restart is necessary.
Some additional information on the mechanism used for this behavior, and how to enable it in Podman, would be very useful.
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
When running containers in systemd services, use the restart functionality provided by systemd. In other words, do not use this option in a container unit, instead set the Restart= systemd directive in the [Service] section. See podman-systemd.unit(5) and systemd.service(5).
Describe your use-case which is not covered by existing documentation.
I'm running Jenkins in Podman (not my choice), and the auto-restart policy described here https://www.jenkins.io/blog/2022/05/27/docker-image-new-lifecycle/ doesn't work. I'm sure it's an issue with Podman and not Jenkins, but I still have to manually reset the Jenkins controller container whenever updating plugins or any other restart is necessary.
Some additional information on the mechanism used for this behavior, and how to enable it in Podman, would be very useful.
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
https://www.jenkins.io/blog/2022/05/27/docker-image-new-lifecycle/
The text was updated successfully, but these errors were encountered: