Watchtower didn't find any other container #673
-
My configuration looks like:
I have some other containers running like My logfile looks like this: $ docker logs 662d36ffe6b2
WARNING: Error loading config file: /root/.docker/config.json: EOF
time="2020-11-07T13:46:11Z" level=debug
time="2020-11-07T13:46:11Z" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."
time="2020-11-07T13:46:12Z" level=debug msg="Retrieving running containers"
time="2020-11-07T13:46:12Z" level=debug msg="There are no additional watchtower containers"
time="2020-11-07T13:46:12Z" level=info msg="Starting Watchtower and scheduling first run: 2020-11-07 13:47:12 +0000 UTC m=+60.588456543"
Failed to send notification email: 535 5.7.8 Username and Password not accepted. Learn more at
5.7.8 https://support.google.com/mail/?p=BadCredentials t5sm6872277wmg.19 - gsmtp
time="2020-11-07T13:47:12Z" level=debug msg="Checking containers for updated images"
time="2020-11-07T13:47:12Z" level=debug msg="Retrieving running containers"
time="2020-11-07T13:47:12Z" level=debug msg="Pulling containrrr/watchtower:latest for /watchtower"
time="2020-11-07T13:47:12Z" level=debug msg="No credentials for containrrr in /config.json"
time="2020-11-07T13:47:12Z" level=debug msg="Got image name: containrrr/watchtower:latest"
time="2020-11-07T13:47:13Z" level=debug msg="No new images found for /watchtower"
time="2020-11-07T13:47:13Z" level=debug msg="This is the watchtower container /watchtower"
time="2020-11-07T13:47:13Z" level=debug msg="Scheduled next run: 2020-11-07 13:48:12 +0000 UTC" I didn't understand the My real problem: Why watchtower is not checking the other container for new images? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 6 replies
-
Looks like watchtower doesn't have access to your config.json. Does watchtower find any other containers if you don't mount the config? |
Beta Was this translation helpful? Give feedback.
-
The config.json is empty. I don't know how "not to mount the config" because I don't know why watchtower is trying to read the config.json. Thanks |
Beta Was this translation helpful? Give feedback.
-
So, i changed two things:
Now the logfile does not have any errors or warnings: But the problem is still: No other containers.... |
Beta Was this translation helpful? Give feedback.
-
Well thx - Bit stupid from my side. 👍 But I think I didn't understand something. time="2020-11-07T22:06:54Z" level=debug
time="2020-11-07T22:06:54Z" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."
time="2020-11-07T22:06:55Z" level=debug msg="Retrieving running containers"
time="2020-11-07T22:06:55Z" level=debug msg="There are no additional watchtower containers"
time="2020-11-07T22:06:55Z" level=info msg="Starting Watchtower and scheduling first run: 2020-11-07 22:07:55 +0000 UTC m=+60.833122914"
time="2020-11-07T22:07:55Z" level=debug msg="Checking containers for updated images"
time="2020-11-07T22:07:55Z" level=debug msg="Retrieving running containers"
time="2020-11-07T22:07:55Z" level=debug msg="Scheduled next run: 2020-11-07 22:08:55 +0000 UTC" Which means the removal of "watchtower" helps to remove th "pulling" messages. For a double check I changed the command line again: Now i expected to get the same messages as at the beginning but with nextcloud instead of watchtower. |
Beta Was this translation helpful? Give feedback.
-
no If you don't mind, pasting the input from |
Beta Was this translation helpful? Give feedback.
-
Crazy thing, tried this direct from commandline instead of docker-compose:
... and it's working. Next step: Now it's more or less back to the old config (With schedule instead of interval, but interval worked also and without timezone because it's not changed to german local time):
... and what should i say: It's working... And yes: you are right, the correct name for the container was nextcloud-nextcloud - But it also not worked earlier. |
Beta Was this translation helpful? Give feedback.
Crazy thing, tried this direct from commandline instead of docker-compose:
... and it's working.
Next step:
I removed all additional configuration (as mail, aso) from the
compose.xml
file... and it's also working.
Now it's more or less back to the old config (With schedule instead of interval, but interval worked also and without timezone because it's not changed to german local time):