From 504d1fc865d8e6af69d4f6d937470e7d587ef736 Mon Sep 17 00:00:00 2001 From: Ross Patterson Date: Sat, 6 Sep 2025 01:55:39 -0700 Subject: [PATCH] docs(automate): Clarify Docker daemon restarts --- .../guides/getting_started/automating_downloads.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/source/guides/getting_started/automating_downloads.rst b/docs/source/guides/getting_started/automating_downloads.rst index be5f1c80..b9148166 100644 --- a/docs/source/guides/getting_started/automating_downloads.rst +++ b/docs/source/guides/getting_started/automating_downloads.rst @@ -41,10 +41,10 @@ schedule. Using ``CRON_RUN_ON_START`` is not recommended because it may cause your cron script to run too often and may trigger throttles and bans. When enabled, your cron script will run *whenever* the container starts including when the host reboots, when ``# - dockerd`` is upgraded, when a new image is pulled, when something applies Compose - changes, etc.. This may result in running ``ytdl-sub`` right before or after the next - cron scheduled run. Instead, run your cron script manually inside the running - container as needed: + dockerd`` restarts such as when upgrading Docker itself, when a new image is pulled, + when something applies Compose changes, etc.. This may result in running ``ytdl-sub`` + right before or after the next cron scheduled run. Instead, run your cron script + manually inside the running container as needed: .. code-block:: console