-
Notifications
You must be signed in to change notification settings - Fork 893
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
Containers created with docker compose
cannot be updated
#1019
Comments
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! 🙏 |
So for some reason, My guess is that it has something to do with the Docker Desktop binary aliases 🤷♀️ |
If this actually gives different results depending on which of the docker container inspect weblate-docker-compose_weblate_1 -f ' Image: {{ .Image }}{{"\n"}}Config.Image: {{.Config.Image}}' (result should look similar to this:) Image: sha256:dd78a816fb764ac6f44bd30d599e3605ebce50bc987e627573ab495092561a69
Config.Image: containrrr/watchtower If not, then the difference is somewhere deeper in the API, which may be much harder to report... Update: Inspect output$ docker container inspect kafka -f ' Image: {{ .Image }}{{"\n"}}Config.Image: {{.Config.Image}}'
Image: sha256:d694642b6bef4693082bd6192d923f37af9e27ef15beef9de7d93a51d1a5d74d
Config.Image: sha256:d694642b6bef4693082bd6192d923f37af9e27ef15beef9de7d93a51d1a5d74d |
With an additional intermediate step, you could still figure it out: I assume, you could use this to get the real image repo from the SHA ID. |
Well, in cases where the image is only tagged once, but that is rarely the case with
So we might end up switching to another tag... |
docker compose
on Win/WSL2docker compose
cannot be updated
Having the same issue. I have installed all my docker images using stacks through Portainer. Some images can't be checked, while other can. Running on RaspberryPi OS and with OpenMediaVault |
See #1050 for the main issue about this. |
It seems like it was fixed in https://github.com/docker/compose-cli/releases/tag/v1.0.18 by docker-archive/compose-cli#2038 @UncleSamSwiss , can you check it out? |
Thanks for the heads-up. Unfortunately I'm no longer using docker compose with watchtower as I moved to k8s. So I don't have an easy way to test this. |
Closing this as I have a very hard time convincing myself that this is something Watchtower should even try to work around. |
Hello , so I am facing same issue getting 401 unauthorized while using watchtower with docker-compose & github organization. Is this issue resolved. Can someone give me a fix. Thanks |
This is a completely different issue. You can pass auth info in the environment variables. |
I passed in the auth info in environment variables, I am still getting the same error |
Make a new issue please and stop hijacking this old one. |
Describe the bug
Using
docker compose
under Windows 10 with Docker in WSL2 leads to wrong image name being used, thus watchtower can't check for updates properly.To Reproduce
docker compose up
(no hyphen!)docker compose down
docker-compose up
(with hyphen!)docker-compose down
Expected behavior
Both
docker-compose up
anddocker compose up
should work the same way.Logs
Below are extracts of the log file of both runs.
Using docker compose:
Using docker-compose:
Main differences:
Environment
Additional context
My docker-compose.yml
Of course you need a docker-compose.override.yml, but I can't provide it here for obvious reasons (credentials).
The text was updated successfully, but these errors were encountered: