Replies: 3 comments 3 replies
-
okay I have run the command on debug mode The issue seems to be I am getting 401 unauthorized response for every request of docker hub. How to solve the issue? I'm also attaching the docker debug response: time="2023-08-18T01:32:23Z" level=debug msg="Trying to load authentication credentials." container=/template-service image="docker.io/akib89/template-manager:v1.1.0"
time="2023-08-18T01:32:23Z" level=debug msg="No credentials for docker.io found" config_file=/config.json
time="2023-08-18T01:32:23Z" level=debug msg="Got image name: docker.io/akib89/template-manager:v1.1.0"
time="2023-08-18T01:32:23Z" level=debug msg="Checking if pull is needed" container=/template-service image="docker.io/akib89/template-manager:v1.1.0"
time="2023-08-18T01:32:23Z" level=debug msg="Building challenge URL" URL="https://index.docker.io/v2/"
time="2023-08-18T01:32:24Z" level=debug msg="Got response to challenge request" header="Bearer realm=\"https://auth.docker.io/token\",service=\"registry.docker.io\"" status="401 Unauthorized"
time="2023-08-18T01:32:24Z" level=debug msg="Checking challenge header content" realm="https://auth.docker.io/token" service=registry.docker.io
time="2023-08-18T01:32:24Z" level=debug msg="Setting scope for auth token" image=docker.io/akib89/template-manager scope="repository:akib89/template-manager:pull"
time="2023-08-18T01:32:24Z" level=debug msg="No credentials found."
time="2023-08-18T01:32:24Z" level=debug msg="Parsing image ref" host=index.docker.io image=docker.io/akib89/template-manager normalized="docker.io/akib89/template-manager:v1.1.0" tag=v1.1.0
time="2023-08-18T01:32:24Z" level=debug msg="Doing a HEAD request to fetch a digest" url="https://index.docker.io/v2/akib89/template-manager/manifests/v1.1.0"
time="2023-08-18T01:32:25Z" level=debug msg="Found a remote digest to compare with" remote="sha256:dd533eddb54bdb1bc04d346fcd29d89d75f8afdb52d0d1692dac1afa73747169"
time="2023-08-18T01:32:25Z" level=debug msg=Comparing local="sha256:dd533eddb54bdb1bc04d346fcd29d89d75f8afdb52d0d1692dac1afa73747169" remote="sha256:dd533eddb54bdb1bc04d346fcd29d89d75f8afdb52d0d1692dac1afa73747169"
time="2023-08-18T01:32:25Z" level=debug msg="Found a match"
time="2023-08-18T01:32:25Z" level=debug msg="No pull needed. Skipping image."
time="2023-08-18T01:32:25Z" level=debug msg="No new images found for /template-service" |
Beta Was this translation helpful? Give feedback.
-
How did you do this? Watchtower reports that it checked one container for an updated image, but found no newer version. If you use the version tags in the screenshot above it won't work, since watchtower only checks images with the same tag. If you want "latest minor' updates, you need to tag your images with both Then you would start your container with |
Beta Was this translation helpful? Give feedback.
-
I think I'm understanding something If the image with tag v1.4.0 is updated in the remote then the watchtower will work and since my version is changed It is not pulling the image. Is there any way to use like this behavior? i.e. It will check based on the version number present in the repository? |
Beta Was this translation helpful? Give feedback.
-
I Have down graded one of docker container version specifically to test this my current Dockerfile is like this:
and my run command looks like this:
docker run -d --name watchtower-container -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock my-watchtower-image
and I have tagged my container perfectly. But this is the log of the watch tower when I manually trigger from the end point of watchtower
May be I'm doing something wrong. My current Image version is 1.4.0 and the latest is 1.5.1
Beta Was this translation helpful? Give feedback.
All reactions