opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-06-22 09:58:10 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #19451 from rhatdan/quadlet

Browse Source 
[CI:DOCS] Mention TimeoutStartSec in quadlet man page
This commit is contained in:
Daniel J Walsh
2023-07-31 14:17:53 -04:00
committed by GitHub
parent 9e91873c26 4f1f88d7c3
commit 94743d4e76
1 changed files with 12 additions and 0 deletions
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, /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. 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 ### Enabling unit files
@ -895,6 +905,8 @@ Exec=sleep 60
[Service] [Service]
# Restart service when sleep finishes # Restart service when sleep finishes
Restart=always Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900
[Install] [Install]
# Start by default on boot # Start by default on boot