-
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-system-generator ignores RemainAfterExit from .build Quadlet #24322
Comments
@ygalblum @alexlarsson @vrothberg Why are we setting RemainAfterExit in quadlet at all? |
Quadlet sets |
What should the default for build be though, shouldn't it attempt a rebuild on each restart? |
Is there a way to check if the user set this? |
Yes. We do something similar for podman/pkg/systemd/quadlet/quadlet.go Line 574 in 1ca42f0
Not sure |
Fixes: containers#24322 Signed-off-by: Daniel J Walsh <[email protected]>
Fixes: containers#24322 Signed-off-by: Daniel J Walsh <[email protected]>
Fixes: containers#24322 Signed-off-by: Daniel J Walsh <[email protected]>
Fixes: containers#24322 Signed-off-by: Daniel J Walsh <[email protected]>
Fixes: containers#24322 Signed-off-by: Daniel J Walsh <[email protected]>
Issue Description
I've created a
.build
quadlet file which runs perfectly at the user context. Since the service is supposed to be started by a systemd.timer I've setRemainAfterExit=no
, but thepodman-system-generator
generates a systemd.service file where the OptionRemainAfterExit
ist set toyes
.Therefore the service never stops and can not be started again by a systemd.timer
Steps to reproduce the issue
Steps to reproduce the issue
hetznerDNSUpdate.build
file:/usr/lib/systemd/system-generators/podman-system-generator --user --dryrun
Describe the results you received
At the
[Service]
Section the Option is set toRemainAfterExit=yes
Describe the results you expected
At the
[Service]
Section the Option is set toRemainAfterExit=no
as specified in thehetznerDNSUpdate.build
File.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Baremetal Fedora Server 40
Additional information
None
The text was updated successfully, but these errors were encountered: