-
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
quadlet should be able to configure the container stop timeout #21134
Comments
Does I would think TimeoutStopSec should do it as well. |
@vrothberg @ygalblum WDYT? |
|
Right move it up to the [Service] definition of the quadlet. |
This message comes from Podman and not from systemd. Meaning, it is the What needs to be set is the |
I added |
It is interesting that StopTimeout is documented in the podman unit file documentation. However, when adding it to the [Container] group of a .container file as described it results in the following error during a dryrun
Is StopTimeout coming in a future podman release, or has it been deprecated, or why is it still documented? |
@jensk-dev this is known issue with the documentation site. The link you added points to the |
Feature request description
I'm using mysql with quadlet and when shutting down the service, there's a warning:
StopSignal SIGTERM failed to stop container systemd-mysql in 10 seconds, resorting to SIGKILL
. In my case, I think I need about 20 seconds for a clean shutdown, but there does not seem to be a way to change the setting.Suggest potential solution
It should be possible for a container unit to configure the stop timeout
Have you considered any alternatives?
At first
TimeoutStopSec=
seemed like a possible solution but it does not appear to have any effect.I suppose it's possible to run quadlet directly, edit the generated service, and use that file instead. But I'd rather not
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: