opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-11-29 17:48:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #27584 from salim-b/patch-1

Browse Source 
docs: improve note about Quadlet TimeoutStartSec
This commit is contained in:
Brent Baude
2025-11-24 09:34:21 -06:00
committed by GitHub
parent 7958d910aa 7b30d9cd3f
commit 90a03ca080
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/source/markdown/podman-systemd.unit.5.md
View File

@@ -85,14 +85,13 @@ or [DynamicUser](https://www.freedesktop.org/software/systemd/man/latest/systemd
systemd options. If you want to run a rootless Quadlet, you will need to create the user systemd options. If you want to run a rootless Quadlet, you will need to create the user
and add the unit file to one of the above rootless unit search paths. and add the unit file to one of the above rootless unit search paths.
Note: When a Quadlet is starting, Podman often pulls or builds one more container images which may take a considerable amount of time. When a Quadlet unit starts, Podman may need to pull or build container images, which can take significantly longer
Systemd defaults service start time to 90 seconds, or fails the service. Pre-pulling the image or extending than systemd's default 90-second service startup limit. If this causes the unit to fail, you can either pre-pull the
the systemd timeout time for the service using the *TimeoutStartSec* Service option can fix the problem. required images or increase the service's startup timeout using the *TimeoutStartSec* option. Keep in mind, however,
A word of caution: *TimeoutStartSec* is not available for `Type=oneshot` units. Refer to `systemd.service(5)` that *TimeoutStartSec* cannot be used with units that specify `Type=oneshot` (their startup timeout is disabled by
for more information on how to handle long startup times for units which do not need to stay active default). For further details on *TimeoutStartSec*, see `systemd.service(5)`.
once their main process has finished.
Adding the following snippet to a Quadlet file extends the systemd timeout to 15 minutes. Adding the following snippet to a Quadlet file extends the startup timeout to 15 minutes.
``` ```
[Service] [Service]
@@ -2373,7 +2372,7 @@ Image=quay.io/example/my-app:latest
Mount=type=artifact,source=my-artifact.artifact,destination=/etc/config Mount=type=artifact,source=my-artifact.artifact,destination=/etc/config
``` ```
Example for Container in a Pod: Example for a container in a Pod:
`test.pod` `test.pod`
``` ```
@@ -2389,7 +2388,7 @@ Exec=sh -c "sleep inf"
Pod=test.pod Pod=test.pod
``` ```
Example for a Pod with a oneshot Startup Task: Example for a Pod with a one-shot startup task:
`test.pod` `test.pod`
``` ```