Docker Containers Won't Update

[dgallaher]

I have a few docker containers that won't update. They show an update available (apply update), complete the regular update process via GUI, and then afterwards still show that an update is available.

 

This is happening with a few select docker containers (binhex-plex, linuxserver/qbittorrent, linuxserver/transmission), but not all. Other dockers are updating successfully.

 

Here is the relevant part of the syslog from when I tried to update one this morning:

Jul 16 11:47:24 dunbar webGUI: Successful login user root from 192.168.0.136
Jul 16 11:47:40 dunbar kernel: docker0: port 1(vethce1f00c) entered disabled state
Jul 16 11:47:40 dunbar kernel: veth2b61baa: renamed from eth0
Jul 16 11:47:41 dunbar avahi-daemon[10305]: Interface vethce1f00c.IPv6 no longer relevant for mDNS.
Jul 16 11:47:41 dunbar avahi-daemon[10305]: Leaving mDNS multicast group on interface vethce1f00c.IPv6 with address fe80::e81c:daff:fe3b:d63f.
Jul 16 11:47:41 dunbar kernel: docker0: port 1(vethce1f00c) entered disabled state
Jul 16 11:47:41 dunbar kernel: device vethce1f00c left promiscuous mode
Jul 16 11:47:41 dunbar kernel: docker0: port 1(vethce1f00c) entered disabled state
Jul 16 11:47:41 dunbar avahi-daemon[10305]: Withdrawing address record for fe80::e81c:daff:fe3b:d63f on vethce1f00c.
Jul 16 11:47:49 dunbar kernel: docker0: port 1(vethe346b53) entered blocking state
Jul 16 11:47:49 dunbar kernel: docker0: port 1(vethe346b53) entered disabled state
Jul 16 11:47:49 dunbar kernel: device vethe346b53 entered promiscuous mode
Jul 16 11:47:49 dunbar kernel: docker0: port 1(vethe346b53) entered blocking state
Jul 16 11:47:49 dunbar kernel: docker0: port 1(vethe346b53) entered forwarding state
Jul 16 11:47:49 dunbar kernel: docker0: port 1(vethe346b53) entered disabled state
Jul 16 11:48:02 dunbar kernel: eth0: renamed from veth0359162
Jul 16 11:48:02 dunbar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe346b53: link becomes ready
Jul 16 11:48:02 dunbar kernel: docker0: port 1(vethe346b53) entered blocking state
Jul 16 11:48:02 dunbar kernel: docker0: port 1(vethe346b53) entered forwarding state
Jul 16 11:48:04 dunbar avahi-daemon[10305]: Joining mDNS multicast group on interface vethe346b53.IPv6 with address fe80::34c6:e0ff:fe10:734f.
Jul 16 11:48:04 dunbar avahi-daemon[10305]: New relevant interface vethe346b53.IPv6 for mDNS.
Jul 16 11:48:04 dunbar avahi-daemon[10305]: Registering new address record for fe80::34c6:e0ff:fe10:734f on vethe346b53.*.
Jul 16 11:51:53 dunbar kernel: veth5b3491c: renamed from eth0
Jul 16 11:51:53 dunbar kernel: docker0: port 2(vethb82f3a7) entered disabled state
Jul 16 11:51:55 dunbar avahi-daemon[10305]: Interface vethb82f3a7.IPv6 no longer relevant for mDNS.
Jul 16 11:51:55 dunbar avahi-daemon[10305]: Leaving mDNS multicast group on interface vethb82f3a7.IPv6 with address fe80::8ceb:f5ff:fe26:9c7b.
Jul 16 11:51:55 dunbar kernel: docker0: port 2(vethb82f3a7) entered disabled state
Jul 16 11:51:55 dunbar kernel: device vethb82f3a7 left promiscuous mode
Jul 16 11:51:55 dunbar kernel: docker0: port 2(vethb82f3a7) entered disabled state
Jul 16 11:51:55 dunbar avahi-daemon[10305]: Withdrawing address record for fe80::8ceb:f5ff:fe26:9c7b on vethb82f3a7.
Jul 16 11:52:13 dunbar kernel: docker0: port 2(vethe496117) entered blocking state
Jul 16 11:52:13 dunbar kernel: docker0: port 2(vethe496117) entered disabled state
Jul 16 11:52:13 dunbar kernel: device vethe496117 entered promiscuous mode
Jul 16 11:52:13 dunbar kernel: docker0: port 2(vethe496117) entered blocking state
Jul 16 11:52:13 dunbar kernel: docker0: port 2(vethe496117) entered forwarding state
Jul 16 11:52:13 dunbar kernel: docker0: port 2(vethe496117) entered disabled state
Jul 16 11:52:20 dunbar kernel: eth0: renamed from veth9929264
Jul 16 11:52:20 dunbar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe496117: link becomes ready
Jul 16 11:52:20 dunbar kernel: docker0: port 2(vethe496117) entered blocking state
Jul 16 11:52:20 dunbar kernel: docker0: port 2(vethe496117) entered forwarding state
Jul 16 11:52:22 dunbar avahi-daemon[10305]: Joining mDNS multicast group on interface vethe496117.IPv6 with address fe80::20cc:95ff:fed6:9568.
Jul 16 11:52:22 dunbar avahi-daemon[10305]: New relevant interface vethe496117.IPv6 for mDNS.
Jul 16 11:52:22 dunbar avahi-daemon[10305]: Registering new address record for fe80::20cc:95ff:fed6:9568 on vethe496117.*.

 

Not sure where to start on troubleshooting this. I've tried switching DNS servers at my router but that doesn't seem to help. Thanks in advance for any help that can point me in the right direction.

 

[Squid]

What version of the OS

[dgallaher]

The latest stable, 6.9.2.

[Squid]

Post your diagnostics

[dgallaher]

Thank you

dunbar-diagnostics-20210717-2252.zip

[Squid]

Any chance you're using user scripts (or another method) to patch some of the docker files (eg: to fix an issue with 6.8.3 not being able to see updates to containers after a change at dockerHub?)

[dgallaher]

Nope, and the only user scripts I run are to regularly (daily or weekly) restart a couple docker containers.

[Squid]

will a new container install?

[dgallaher]

Yes, I can install new containers and most other currently installed containers update normally.

[dgallaher]

Just an update: the same containers still fail to update most of the time. As a terrible workaround I just set them to auto update via the CA plugin and eventually the updates stick. 🤷‍♂️