nils måsén

Hello! Sure, @11-aryan. I'd be happy to review it!

Actually, I think this is already implemented? Looking at the code: https://github.com/containrrr/watchtower/blob/284066a39d083fe4865ae43119a41b42d450b178/pkg/lifecycle/lifecycle.go#L101-L105 It already adds an error log message (which will be sent in notifications) if the post update hook...

@wmandra There isn't any fix. Swarm pins the container images to specific hashes which means that the latest version of the image is always the same. Even if watchtower would...

Watchtower doesn't use commands, it's communicating directly with the docker daemon through the [api](https://docs.docker.com/engine/api/v1.41). If you want to run swarm-specific stuff, it seems like it would be easier to use...

@t-keller docker swarm. Even though it's not visible in `docker ps`, it's still present in `docker inspect` (which gives the same information that the API/watchtower gets).

@ribbons Yeah, that might be the case. I tried to follow the lookups to see if it shouldn't be needed for some reason, but I think you are right. It...

Yeah, sorry. It works for me, and you are giving me very little to work with.

@wolfcdd, I don't know what you are trying to do, but create a new issue, since it doesn't seem related to this one.

This should actually be possible now using regex container matching. If your project prefix is `myproject`, you could run watchtower with: ```yaml services: watchtower: image: containrrr/watchtower command: "^myproject-.*" volumes: -...

Well, the error itself is that it's trying to make DNS lookup of the domain name `api.pushover.net` through the default DNS server (`localhost`, which is being resolved as `::1`, which...