monitor-only requirement about watchtower HOT 6 OPEN

It seems like you would be better off using https://github.com/crazy-max/diun instead. The core of watchtower is implemented using communication with the docker service, requiring to pull the images. You could talk directly to the docker registries instead, but that would be a wholly different code path that just isn't implemented.

from watchtower.

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏

from watchtower.

I have the same Problem.

It is explained in the documentation:

"Due to Docker API limitations the latest image will still be pulled from the registry. The HEAD digest checks allows watchtower to skip pulling when there are no changes, but to know what has changed it will still do a pull whenever the repository digest doesn't match the local image digest."

Watchtower says that the minimum Docker-API version is 1.24 but the latest API version is currently 1.43

Maybe the behavior has changed since the documentation was written?

from watchtower.

@obzocker I'm not sure what you mean... The docs explain why it's pulling the image. There could be code added that would skip the pulling for monitor-only, but it's not an easy fix.

from watchtower.

@piksel I understand why this is the expected behaviour but it is still a problem.

Watchtower still makes changes in monitor-only mode, which messes up the tags of already started containers.

You loose easy access to metadata when using watchtower with e.g. Portainer. The started container does no longer show the associated tag but the short hash. This is very confusing for people who only do maintenance on these systems.

Furthermore as described by @luweijun1992 you loose reproducibility when you e.g. change a small detail in a stack/compose.

e.g. in Portainer you have the option to change the stack but NOT repull and redeploy the images. If watchtower has already pulled the image in through the monitor-only mode the stack still gets updated which is not desirable.

Is there an easier way to check for a new Docker image without pulling it directly, perhaps due to changes in the Docker API?

from watchtower.

This problem is exacerbated by the systemd timer on my host that periodically restarts containers. And, though I don't run many containers, nor have I been running them for long, I already had 2 cases where manual intervention was required to fix a problem after an image update.

Therefore, I'll be switching to duin. Thanks a lot @piksel for pointing me to that 👍!

from watchtower.