jenkins.io icon indicating copy to clipboard operation
jenkins.io copied to clipboard

Add help for auto-restarts in Podman

Open mcascone opened this issue 1 year ago • 1 comments
trafficstars

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/

mcascone avatar Feb 19 '24 17:02 mcascone

Hello @mcascone , could you describe:

  • The command line or options you are using to start Jenkins (so both you and us can double check the restart policy)
  • Describe the exact steps you are doing so we could reproduce?

Note: as per https://docs.podman.io/en/latest/markdown/podman-run.1.html#restart-policy, you might be in the case of podman using the systemd restart system:

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).

Could you check with your admins?

dduportal avatar Feb 19 '24 17:02 dduportal