mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-13 20:29:35 +00:00
7c54d14232
Remove the container in ExecStop to make sure that Quadlet's adheres to Podman's customizable stop signal/timeout. Certain programs ignore SIGTERM which renders the services generated by Quadlet less user friendly compared to the ones from podman-generate-systemd. Previously, `systemctl stop` would just hang until systemd's stop timeout is hit. Since `podman rm` also removes the CID file, the additional `rm` can be removed. Note that `podman rm` will return immediately if the specified CID file isn't present. I am working on a short tutorial on Quadlet and hit the issue with a simple container running `sleep`. `sleep` ignores SIGTERM and stopping the service would take forever even with `PodmanArgs=--stop-timeout=0`. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com> |
||
|---|---|---|
| .. | ||
| define | ||
| generate | ||
| notifyproxy | ||
| parser | ||
| quadlet | ||
| activation.go | ||
| activation_test.go | ||
| dbus.go | ||