NC AIO with isolated external Watchtower instance?

[a_kemper]

Hi,

I’m running a server with NC AIO and some other containerized services on it.

In order to keep the other services up-to-date while not touching AIOs update mechanism, I started the mastercontainer with something like labels = “com.centurylinklabs.watchtower.enable=false”. Unfortunately it seems that already the presence of the external Watchtower instance seems to break AIOs update mechanism, i. e. I get frequent notifications for updates even when none are available and the GUI-based update of the mastercontainer isn’t possible anymore.
Now my idea is basically to separate the docker sockets for the NC containers from all the others, e. g. by switching from docker.sock to docker-nc.sock. Would this work or will Docker itself run into issues when connectd to multiple sockets?

Thx
Andreas

[vawaver]

The easiest way is not to mess with multiple docker sockets at all.
Just run Watchtower with label filtering enabled and add the label only to containers you actually want it to update.

In docker-compose.yml of Watchtower:

environment:
  - WATCHTOWER_LABEL_ENABLE=true

And then in the compose files of your non-AIO services:

labels:
  - "com.centurylinklabs.watchtower.enable=true"

That way Watchtower completely ignores all AIO containers and only updates the ones you explicitly mark.

[a_kemper]

Thanks, that sounds like a good option. By now I tried to exclude the NC containers, but it could be easier to explicitly enable only the others.

Could it potentially happen that the NC-internal Watchtower tries to update the other containers or will they be ignored / does NC these days anyhow use a different update mechanism?

[vawaver]

I‘m using exactly this setup myself and it works flawlessly.

The Watchtower that comes with Nextcloud AIO is separate and only takes care of the AIO containers. It won’t touch any of your other services, so there’s no conflict with the default Watchtower you run for the rest.