From 4f1f88d7c34b4dd299fa845c23f6eff516d90618 Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Mon, 31 Jul 2023 10:41:58 -0400 Subject: [PATCH] Mention TimeoutStartSec in quadlet man page Signed-off-by: Daniel J Walsh --- docs/source/markdown/podman-systemd.unit.5.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/source/markdown/podman-systemd.unit.5.md b/docs/source/markdown/podman-systemd.unit.5.md index 3542c4c9a2..1ec0f7a9d6 100644 --- a/docs/source/markdown/podman-systemd.unit.5.md +++ b/docs/source/markdown/podman-systemd.unit.5.md @@ -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