You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
At container startup, Diun lauches the update check, as it is explained in the comment #833 (comment).
In my use case, my container is stopped every night because installed on Synolog NAS that shutdown every night, and every morning Diun check updates, despite i set it up to check only on sundays.
Expected behaviour
Add a new config parameter to activate or not the run at startup in addition with the cron trigger.
Actual behaviour
Run is launched at startup and when triggered by cron.
Steps to reproduce
Start Diun container
Check is done immediatly even if the moment does not satisfy the cron
Support guidelines
I've found a bug and checked that ...
Description
At container startup, Diun lauches the update check, as it is explained in the comment #833 (comment).
In my use case, my container is stopped every night because installed on Synolog NAS that shutdown every night, and every morning Diun check updates, despite i set it up to check only on sundays.
Expected behaviour
Add a new config parameter to activate or not the run at startup in addition with the cron trigger.
Actual behaviour
Run is launched at startup and when triggered by cron.
Steps to reproduce
Diun version
4.24.0
Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: