You are not logged in.

#1 2020-03-24 14:30:15

daweed
Member
Registered: 2020-03-24
Posts: 2

Docker networking broken after pacman -Syu

So here I am doing just a regular update. Finishes fine, no errors. I stop all my containers and reboot.

After reboot everything is messed up in docker:
- DNS no longer works (not even fixed by addong --dns 1.1.1.1)
- Communication between containers in the same bridge network is broken (wtf)
- Communication between bridge networks doesn't work (expected)
- Host can ping containers but they can't ping eachother...

tested with:

docker run --rm busybox ping -c 1 1.1.1.1

-> 64 bytes from 1.1.1.1: seq=0 ttl=57 time=4.160 ms

docker run --rm busybox nslookup example.com

-> nslookup: write to '192.168.1.1': No route to host

docker run --rm --dns 1.1.1.1 busybox nslookup example.com

-> nslookup: write to '1.1.1.1': No route to host

docker network create -d bridge --internal --gateway 172.18.0.1 --subnet 172.18.0.0/16 testnet
docker run -it --rm --network=testnet --ip 172.18.10.10 subfuzion/netcat -vl 8888
another terminal: docker run -i --rm --network=testnet subfuzion/netcat 172.18.10.10 8888 < /etc/passwd

-> f1b323ef3c02d58cf07a00fc1960becf1c1377399115ad4c6a117cdacd99aa20
-> Listening on [0.0.0.0] (family 0, port 8888)
-> no output

Yes, I have checked sysctl, ipv4 forwarding is enabled for all interfaces.
I did nothing else other than update from 2020-02-29 to 2020-03-24 (I update some time at the end of each month)

Update: using the arch linux archives (mirrorlist below), downgrading the packages (pacman -Syyuu) and rebooting did NOT fix the issues. Now I'm even more clueless...

Server = https://archive.archlinux.org/repos/2020/02/29/$repo/os/$arch

Update #2: Tried updating another arch machine I run and the output of the above commands is what I would expect - networking between containers is not broken and the listening side of netcat outputs the data that is read in. This is starting to feel like I'm going to have to completely remove everything docker related and do it some other way...

Last edited by daweed (Today 19:07:01)

Offline

#2 Today 17:39:02

daweed
Member
Registered: 2020-03-24
Posts: 2

Re: Docker networking broken after pacman -Syu

Nobody??? Seriously?

Offline

#3 Today 18:58:07

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,502
Website

Re: Docker networking broken after pacman -Syu


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Online

Board footer

Powered by FluxBB