-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does wud check for updates when running docker compose up -d? #548
Comments
Hi, In your log, I can see several Besides, because you set Can it explain what you see? |
Yes, the container recreates each time I run Thanks @fmartinou ! |
Hi, I confirm the behavior. It seems that WUD_WATCHER_LOCAL_WATCHEVENTS set to true will run when you are creating or deleting, containers that may not actually watched. My understanding from docs is that this label is to monitor changes in watched containers that are updated, not all of them. In my case, I'm using WUD_WATCHER_LOCAL_WATCHBYDEFAULT=false and WUD_WATCHER_LOCAL_WATCHALL=true. WUD_WATCHER_LOCAL_WATCHEVENTS is set to false avoid this behavior. In any case, thanks for this amazing program. |
Setting There is no other consequences by doing this; it's safe 😃 ! |
Perfect! Thanks a lot! |
Hey!
Just a quick question
This is the relevant part of my docker compose:
And here are my logs:
The context is that I updated some containers and then ran
docker compose up -d
and was not expecting wud to run again since I have set it to run as a cron and explicitly set theWUD_WATCHER_docker_WATCHATSTART
flag as false. However, I got notifications from other containers having new versions.Why does this happen?
The text was updated successfully, but these errors were encountered: