I decided to get with the times and learn about Docker. I currently have various bare metal server instances on a NAS, and wanted to bring some of them over to Docker on my (infinitely more powerful) Threadripper system. Just to get the hang of it, I installed the latest Docker CE on my MacBook Pro. I found that while I could install images and set servers up no problem (bridge networking), after a short while my main (Mac/host) ethernet would just die and get a 169 IP address. No amount of resetting the connection, unplugging and replugging, or anything else would fix it.
If I turned off Docker and quit the app, I could get an IP using DHCP again and my Mac's internet was perfectly fine. Fire up Docker, and it'd drop to a 169 address again and nothing but a manual config would restore connectivity. Weird, but Docker is meant for Linux anyway so I figured I'd try there in the morning...
So today I installed Docker CE (from Docker's own repo) on my Fedora 31 KDE (Threadripper) box. It installed fine, and after a reboot the hello-world image ran and showed no issues. Great... Except now my internet on *this* box, while still connected at least, runs at between 100 to 500 KBps (versus 550 Mbps usually). It was so slow that updates were timing out, web pages refused to load and hung, and I was getting pop up messages from the system asking if I had 'weird power management settings enabled, as the kernel is confused'.
I tried restarting NetworkManager, I tried setting up a manual profile for the connection (as on the MacBook) - but nothing worked. I uninstalled Docker and I'm instantly back to 550Mbps and instant browsing speeds.
Unless I happen to have stumbled on a huge bug in Docker, coincidentally present in the release at the exact same time I decide to try it, something else must be going wrong. Does anyone have any ideas?
If I turned off Docker and quit the app, I could get an IP using DHCP again and my Mac's internet was perfectly fine. Fire up Docker, and it'd drop to a 169 address again and nothing but a manual config would restore connectivity. Weird, but Docker is meant for Linux anyway so I figured I'd try there in the morning...
So today I installed Docker CE (from Docker's own repo) on my Fedora 31 KDE (Threadripper) box. It installed fine, and after a reboot the hello-world image ran and showed no issues. Great... Except now my internet on *this* box, while still connected at least, runs at between 100 to 500 KBps (versus 550 Mbps usually). It was so slow that updates were timing out, web pages refused to load and hung, and I was getting pop up messages from the system asking if I had 'weird power management settings enabled, as the kernel is confused'.
I tried restarting NetworkManager, I tried setting up a manual profile for the connection (as on the MacBook) - but nothing worked. I uninstalled Docker and I'm instantly back to 550Mbps and instant browsing speeds.
Unless I happen to have stumbled on a huge bug in Docker, coincidentally present in the release at the exact same time I decide to try it, something else must be going wrong. Does anyone have any ideas?
The two happening at the same time (Docker install and the speed dropping 550 > 5) was a nice big fat red herring, but I worked it out about an hour later. Always check the basics, and don't make assumptions! You'd think I'd learn. Still, all's well that ends well - and I'm loving Docker.
My question is about linking containers for networking. I can't get my head around it. If I set up a Docker container as a WireGuard client (i.e. it connects to a remove WG server via my WAN and has a VPN/proxied IP), how do I link it to other containers so they are automagically covered by the VPN? I can link containers together for resources like files, but I've not sussed networking even with Whoogle's help. Any tips please?