From d1c2afc94115c0b9444a719f79bbccd706a3f7cc Mon Sep 17 00:00:00 2001 From: Salim B Date: Sat, 22 Nov 2025 00:51:01 +0100 Subject: [PATCH 1/2] docs: improve note about Quadlet TimeoutStartSec Signed-off-by: Salim B --- docs/source/markdown/podman-systemd.unit.5.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/source/markdown/podman-systemd.unit.5.md b/docs/source/markdown/podman-systemd.unit.5.md index d724fb6537..2e4365bc9f 100644 --- a/docs/source/markdown/podman-systemd.unit.5.md +++ b/docs/source/markdown/podman-systemd.unit.5.md @@ -85,12 +85,11 @@ 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 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. -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. -A word of caution: *TimeoutStartSec* is not available for `Type=oneshot` units. Refer to `systemd.service(5)` -for more information on how to handle long startup times for units which do not need to stay active -once their main process has finished. +When a Quadlet unit starts, Podman may need to pull or build container images, which can take significantly longer +than systemd's default 90-second service startup limit. If this causes the unit to fail, you can either pre-pull the +required images or increase the service's startup timeout using the *TimeoutStartSec* option. Keep in mind, however, +that *TimeoutStartSec* cannot be used with units that specify `Type=oneshot` (their startup timeout is disabled by +default). For further details on *TimeoutStartSec*, see `systemd.service(5)`. Adding the following snippet to a Quadlet file extends the systemd timeout to 15 minutes. From 7b30d9cd3fdb171e5f65cc9c99ece3c704bbb3e5 Mon Sep 17 00:00:00 2001 From: Salim B Date: Sat, 22 Nov 2025 01:17:47 +0100 Subject: [PATCH 2/2] docs: further tweaks Signed-off-by: Salim B --- docs/source/markdown/podman-systemd.unit.5.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/markdown/podman-systemd.unit.5.md b/docs/source/markdown/podman-systemd.unit.5.md index 2e4365bc9f..426614080f 100644 --- a/docs/source/markdown/podman-systemd.unit.5.md +++ b/docs/source/markdown/podman-systemd.unit.5.md @@ -91,7 +91,7 @@ required images or increase the service's startup timeout using the *TimeoutStar that *TimeoutStartSec* cannot be used with units that specify `Type=oneshot` (their startup timeout is disabled by default). For further details on *TimeoutStartSec*, see `systemd.service(5)`. -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] @@ -2372,7 +2372,7 @@ Image=quay.io/example/my-app:latest 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` ``` @@ -2388,7 +2388,7 @@ Exec=sh -c "sleep inf" Pod=test.pod ``` -Example for a Pod with a oneshot Startup Task: +Example for a Pod with a one-shot startup task: `test.pod` ```