Skip to content
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

How to disable watchtower on a single container? #169

Closed
Skaronator opened this issue Feb 26, 2018 · 10 comments
Closed

How to disable watchtower on a single container? #169

Skaronator opened this issue Feb 26, 2018 · 10 comments

Comments

@Skaronator
Copy link

The Readme doesn't answer this question directly. I assume setting com.centurylinklabs.watchtower.enable to false will disable updates for a single container? Do I need to change something on my start parameter?

@stffabi
Copy link
Contributor

stffabi commented Feb 27, 2018

Thanks for your report. In order to use the label you have to pass --label-enable after having passed this flag, only containers with the label com.centurylinklabs.watchtower.enable set to true will be updated.

@Skaronator
Copy link
Author

Is there a way to make the exact opposite? I'd like to auto-update all containers except a single one.

@redge76
Copy link

redge76 commented Feb 28, 2018

Exactly what I need for my comment #167 . Unfortunately, it seems there is no safe way to do this.

@stffabi
Copy link
Contributor

stffabi commented Mar 1, 2018

It would be possible to change the behaviour, that containers which have the label com.centurylinklabs.watchtower.enable set to false are always excluded from the updates. Those would be also excluded if the --label-enable wasn't specified.

@redge76 would that be a possible trade-off for you? You would then need to always create your containers with the label set to false.

@redge76
Copy link

redge76 commented Mar 1, 2018

That's better than nothing.
And it's true that the option "--label-enable" has no added value.
If there is a label, then watchtower honors it. If not, default behaviour.
It's now 100% safe because you can always forget to set this label for a new container, but it's a lot better.

@stffabi
Copy link
Contributor

stffabi commented Mar 1, 2018

Yeah, I know it's not the best solution. But it would be a trade-off where we don't break anything for the people out there but at least give some safer behaviour.

@Skaronator
Copy link
Author

Thanks!

@stffabi
Copy link
Contributor

stffabi commented Mar 3, 2018

@Skaronator you're welcome. Please note a new release is scheduled for in about one to two weeks.

darknode pushed a commit to darknode/watchtower that referenced this issue Mar 4, 2018
@redge76
Copy link

redge76 commented May 15, 2018

Hi,
Still no release ?

@Keridos
Copy link

Keridos commented Jul 4, 2018

please release this. My logs are full of spam because of some containers that watchtower wants to update, but fails to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants