Docker is going nuts after I had to reboot for some ‘critical’ update for something else.
Looks like it’s going crazy regarding ARP:
07:27:18.632243 ARP, Request who-has 172.17.0.4 tell 172.17.0.2, length 28
07:27:18.632275 ARP, Reply 172.17.0.4 is-at 02:42:ac:11:00:02, length 28
Of course the weird thing is that 172.17.0.2 doesn’t need to talk to 172.17.0.4 at all.
I keep getting this on the db server:
2018-04-11 9:11:30 139923730724608 [Warning] Aborted connection 4226 to db: ‘virtuall_wp152’ user: ‘root’ host: ‘172.17.0.3’ (Got timeout reading communication packets)
which of course is up the entire time.Â restarting either the web server or the db server puts me up for seconds at a time.
So while I move stuff around, and get ready for a re-install of my base OS, as I can’t seem to figure out why the bridge has freaked out, if you can read this, then the sloppy.io container thing is actually working.Â And at least on the surface, moving container persistent storage, along with a DNS update looks pretty quick.