nils måsén

I just need some free time, I think. Should be able to complete this during the Christmas holidays...

Watchtower does not work with swarm. Try using https://GitHub.com/containrrr/shepherd

Multiple recipients should work fine for shoutrrr. It might be something with the legacy notifications adapter that encodes the commas, perhaps? Try using a shoutrrr URL directly instead: ```yaml WATCHTOWER_NOTIFICATION_URL:...

Interesting! So this was caused by docker compose's environment parsing... Or perhaps it's due to our attempts at cleaning extra quotes that split the input into addresses before removing quotes......

Are you sure this doesn't work? The code you are thinking of is only used for HEAD requests (which I don't even know if GCP support?). It should just fall...

Like I said, it's **always** the docker daemon that does the pull and authentication. The error even contains `Error response from daemon: `. That being said, something is clearly different....

Hm, it says that you should base64 encode it as `_json_key:`, where `` is the full contents of a key file in JSON format. Is this what you are doing?...

What do you mean by: > This is not an issue when creating a config.json and authenticating against the artifact registry manually. Are you saying that using the same config.json...

Interesting! The problem users had before 1.6.0 were that they could not update containers that depended on gluetun for networking. In v1.6.0, support for updating such containers was added and...

@Al4ndil it never worked correctly with rolling restarts and dependent containers. What probably worked for you before was ignoring the dependency and hoping it wouldn't break whenever it was updated.