Dockers Orphan image

[jsoonias]

Hey guys,

 

Hit the update all button for my dockers and the process got stuck on shutting down duckdns. after an hour I exited out of the update window and now have a few orphan images where my dockers should be. Is there an easy way to get these back?

 

Jan 1 19:06:00 Jesse emhttpd: req (15): cmdStartMover=Move+now&csrf_token=****************
Jan 1 19:06:00 Jesse emhttpd: shcmd (7311): /usr/local/sbin/mover &> /dev/null &
Jan 1 19:10:11 Jesse nginx: 2019/01/01 19:10:11 [error] 10254#10254: *529594 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.29, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=duckdns&ct[]=JesseSoonias&ct[]=mariadb&ct[]=openvpn-as HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.49", referrer: "http://192.168.1.49/Docker"
Jan 1 19:13:21 Jesse kernel: veth8196083: renamed from eth0
Jan 1 19:13:21 Jesse kernel: br-d041a9a063a1: port 1(vethe668705) entered disabled state
Jan 1 19:13:23 Jesse avahi-daemon[10107]: Interface vethe668705.IPv6 no longer relevant for mDNS.
Jan 1 19:13:23 Jesse avahi-daemon[10107]: Leaving mDNS multicast group on interface vethe668705.IPv6 with address fe80::ec0c:adff:fe17:21c5.
Jan 1 19:13:23 Jesse kernel: br-d041a9a063a1: port 1(vethe668705) entered disabled state
Jan 1 19:13:23 Jesse kernel: device vethe668705 left promiscuous mode
Jan 1 19:13:23 Jesse kernel: br-d041a9a063a1: port 1(vethe668705) entered disabled state
Jan 1 19:13:23 Jesse avahi-daemon[10107]: Withdrawing address record for fe80::ec0c:adff:fe17:21c5 on vethe668705.
Jan 1 19:16:37 Jesse kernel: veth4f72b13: renamed from eth0
Jan 1 19:16:37 Jesse kernel: docker0: port 1(vethe1d2ce7) entered disabled state
Jan 1 19:16:39 Jesse avahi-daemon[10107]: Interface vethe1d2ce7.IPv6 no longer relevant for mDNS.
Jan 1 19:16:39 Jesse kernel: docker0: port 1(vethe1d2ce7) entered disabled state
Jan 1 19:16:39 Jesse avahi-daemon[10107]: Leaving mDNS multicast group on interface vethe1d2ce7.IPv6 with address fe80::784f:eaff:fede:9dcb.
Jan 1 19:16:39 Jesse kernel: device vethe1d2ce7 left promiscuous mode
Jan 1 19:16:39 Jesse kernel: docker0: port 1(vethe1d2ce7) entered disabled state
Jan 1 19:16:39 Jesse avahi-daemon[10107]: Withdrawing address record for fe80::784f:eaff:fede:9dcb on vethe1d2ce7.
Jan 1 19:17:11 Jesse kernel: docker0: port 1(veth9c2f2ae) entered blocking state
Jan 1 19:17:11 Jesse kernel: docker0: port 1(veth9c2f2ae) entered disabled state
Jan 1 19:17:11 Jesse kernel: device veth9c2f2ae entered promiscuous mode
Jan 1 19:17:11 Jesse kernel: IPv6: ADDRCONF(NETDEV_UP): veth9c2f2ae: link is not ready
Jan 1 19:17:11 Jesse kernel: docker0: port 1(veth9c2f2ae) entered blocking state
Jan 1 19:17:11 Jesse kernel: docker0: port 1(veth9c2f2ae) entered forwarding state
Jan 1 19:17:11 Jesse kernel: docker0: port 1(veth9c2f2ae) entered disabled state
Jan 1 19:17:18 Jesse kernel: eth0: renamed from vetha01a56f
Jan 1 19:17:18 Jesse kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9c2f2ae: link becomes ready
Jan 1 19:17:18 Jesse kernel: docker0: port 1(veth9c2f2ae) entered blocking state
Jan 1 19:17:18 Jesse kernel: docker0: port 1(veth9c2f2ae) entered forwarding state
Jan 1 19:17:19 Jesse avahi-daemon[10107]: Joining mDNS multicast group on interface veth9c2f2ae.IPv6 with address fe80::90f3:3bff:feec:8692.
Jan 1 19:17:19 Jesse avahi-daemon[10107]: New relevant interface veth9c2f2ae.IPv6 for mDNS.
Jan 1 19:17:19 Jesse avahi-daemon[10107]: Registering new address record for fe80::90f3:3bff:feec:8692 on veth9c2f2ae.*.

[jsoonias]

attached is the diagnostics

jesse-diagnostics-20190101-1959.zip

[Squid]

8 minutes ago, jsoonias said:

Is there an easy way to get these back?

Delete all the orphans (or alternatively delete the docker image) then Apps, Previous Apps Section, check off what you want and hit install multi. A coffee (or beer) later and your in business

[jsoonias]

Thanks again squid. That worked

 

any idea on what all the activity in the log means? regarding the port activity?

[Squid]

Normal stuff

[BrockTrainedAsh]

I had this same issue in my diagnostics. Turns out my amcrest2myqtt docker was pointed at an incorrect ip address and kept trying to reconnect in error. Going one by one down my dockers and turning them off is how I found the error. Also, its log was huge.