If I reference this thread it might start the ball rolling in particular this post
Initially I thought I had no issues, but I did notice that that some of the containers had not been updated, so a quick investigation revealed that some should have been. So I checked watchtowers log file, this appeared to working but full of errors relating to watchtower being unable to communicate with the current container list.
So restarted watchtower and waited for it to refresh still the same errors, cleared the log file (mistake!!) and restarted waited 10 mins refreshed checked the log file empty!
Delete the container, delete the image and start again -> the container has now been up for 30+ minutes and this is the content of the log file:
time="2018-11-20T10:20:19Z" level=info msg="First run: 2018-11-20 10:25:19 +0000 GMT" that's it nothing else.
I then ran service docker restart and checked service docker status ->
service docker status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─openmediavault.conf
Active: active (running) since Tue 2018-11-20 10:58:33 GMT; 6s ago
Docs: https://docs.docker.com
Main PID: 28186 (dockerd)
Tasks: 40
Memory: 42.9M
CPU: 1.671s
CGroup: /system.slice/docker.service
├─28186 /usr/bin/dockerd -H unix:///var/run/docker.sock
├─28361 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8000 -container-ip 172.17.0.2 -container-port 8000
├─28417 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8081 -container-ip 172.17.0.3 -container-port 80
└─28476 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 3000 -container-ip 172.17.0.4 -container-port 3000
Nov 20 10:58:30 homenas dockerd[28186]: time="2018-11-20T10:58:30.311526593Z" level=info msg="IPv6 enabled; Adding default IPv6 exter
Nov 20 10:58:30 homenas dockerd[28186]: time="2018-11-20T10:58:30.567919475Z" level=info msg="No non-localhost DNS nameservers are le
Nov 20 10:58:30 homenas dockerd[28186]: time="2018-11-20T10:58:30.568594775Z" level=info msg="IPv6 enabled; Adding default IPv6 exter
Nov 20 10:58:30 homenas dockerd[28186]: time="2018-11-20T10:58:30.719372213Z" level=info msg="No non-localhost DNS nameservers are le
Nov 20 10:58:30 homenas dockerd[28186]: time="2018-11-20T10:58:30.719424421Z" level=info msg="IPv6 enabled; Adding default IPv6 exter
Nov 20 10:58:32 homenas dockerd[28186]: time="2018-11-20T10:58:32.877770085Z" level=info msg="Loading containers: done."
Nov 20 10:58:32 homenas dockerd[28186]: time="2018-11-20T10:58:32.936863438Z" level=info msg="Docker daemon" commit=4d60db4 graphdriv
Nov 20 10:58:32 homenas dockerd[28186]: time="2018-11-20T10:58:32.938134416Z" level=info msg="Daemon has completed initialization"
Nov 20 10:58:33 homenas systemd[1]: Started Docker Application Container Engine.
Nov 20 10:58:33 homenas dockerd[28186]: time="2018-11-20T10:58:33.118366398Z" level=info msg="API listen on /var/run/docker.sock"
Alles anzeigen
The containers are now showing an up time of 12 minutes and the output from the log file is;
time="2018-11-20T10:20:19Z" level=info msg="First run: 2018-11-20 10:25:19 +0000 GMT"
time="2018-11-20T10:58:18Z" level=info msg="Waiting for running update to be finished..."
time="2018-11-20T10:58:33Z" level=info msg="First run: 2018-11-20 11:03:33 +0000 GMT"
As you can see "First run" is 11:03 some 9 minutes previous and that is all that's in the log, considering watchtower is supposed to check every 5 mins something is wrong.
I have also discovered that stopping the container and then modifying errors, in fact the error seems to point to the container being deleted -> odd!
As it doesn't appear to be able to modify the container I'm going to delete it and set the --debug option in the command setting and see if that reveals anything.