-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman generate systemd --restart-sec is not honored by containers #16419
Comments
Thanks for reaching out, @nivekuil ! |
Hi, I'd like to try to take on this one as a first issue, if that's ok :) |
Fine with me. |
Can i also try to work on this issue? |
@Darth-Mera asked first, so I'd very much prefer to keep this order. Please respect that @aadi58002 before opening a PR next time. It's not a race. |
Attempts to fix containers#16419 podman generate systemd --restart-sec pod ^now generates RestartSec= both in pod service file and in container service file. podman generate systemd --restart-sec container ^now generates RestartSec= in container service file. Signed-off-by: Veronika Fuxova <[email protected]>
I pushed my attempt at solving this issue. Not a fan of duplicating work, but I guess we're both learning. |
It was a leaning experience for me as well. I also looked at your PR which is much better and more better done than mine thanks for providing a good experience and learning. |
Thanks to both of you. Nice thing is there are plenty more "good first issues" to work on. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman generate systemd --restart-sec pod
only generatesRestartSec=
in the pod service, not the container service. This basically renders it ineffective since the containers are the ones likely to be restarting.Steps to reproduce the issue:
podman generate systemd --restart-sec 3 my-pod
and inspect the service file of its containerDescribe the results you received:
Describe the results you expected:
Should have
RestartSec=
in thereAdditional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: