danvics/ytdl-sub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(automate): Clarify Docker daemon restarts

Browse source
This commit is contained in:
Ross Patterson 2025-09-06 01:55:39 -07:00
parent 97628e54b2
commit 504d1fc865
No known key found for this signature in database
GPG key ID: 2EFF7CCE6828E359
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/source/guides/getting_started/automating_downloads.rst
View file

@ -41,10 +41,10 @@ schedule.
Using ``CRON_RUN_ON_START`` is not recommended because it may cause your cron script 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 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 ``# 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 dockerd`` restarts such as when upgrading Docker itself, when a new image is pulled,
changes, etc.. This may result in running ``ytdl-sub`` right before or after the next when something applies Compose changes, etc.. This may result in running ``ytdl-sub``
cron scheduled run. Instead, run your cron script manually inside the running right before or after the next cron scheduled run. Instead, run your cron script
container as needed: manually inside the running container as needed:
.. code-block:: console .. code-block:: console