containers
/
podman
mirror of https://github.com/containers/podman.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention TimeoutStartSec in quadlet man page 

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
Daniel J Walsh 2023-07-31 10:41:58 -04:00
parent 330e51960e
commit 4f1f88d7c3
No known key found for this signature in database
GPG Key ID: A2DF901DABE2C028
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -48,6 +48,16 @@ session gets started. For unit files placed in subdirectories within
/etc/containers/systemd/user/${UID}/ and the other user unit search paths,
Quadlet will recursively search and run the unit files present in these subdirectories.
Note: When a Quadlet is starting, Podman often pulls one more container images which may take a considerable amount of time.
Systemd defaults service start time to 90 seconds, or fails the service. Pre-pulling the image or extending
the systemd timeout time for the service using the *TimeoutStartSec* Service option can fix the problem.
Adding the following snippet to a Quadlet file extends the systemd timeout to 15 minutes.
```
[Service]
TimeoutStartSec=900
```
### Enabling unit files
@ -895,6 +905,8 @@ Exec=sleep 60
[Service]
# Restart service when sleep finishes
Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900
[Install]
# Start by default on boot