Psycs Posted April 11, 2019 Share Posted April 11, 2019 (edited) No longer able to reach any of my Dockers after restarting unRaid. Setup unRaid and installed a handful of dockers. Each docker has a static IP address. Everything was working fine until I rebooted unRaid. Now i'm unable to access any of the docker GUI/Web pages, but I can access the console. Tried setting up a new docker, same problem. I can ping each docker from within a docker, but can't ping from any computer to any of the docker IPs and versa . Can't ping from within the docker to the gateway. Each dockers network is set to br2 with a static IP. Everything (unRaid, Computers and Dockers) is running on 192.168.86.0/24 Could use some help figuring this one out. Edited April 11, 2019 by Psycs Quote Link to comment
ken-ji Posted April 11, 2019 Share Posted April 11, 2019 You need to post your diagnostics for complete info, but I can guess the problem and solution. Do not assign an IP to the br2 network interface. it is causing unraid to be accessible on both interfaces, but the dockers are only on one and its probably the wrong one now. Recreate the custom docker network on br2 (after removing the docker network on eth0) Quote Link to comment
Psycs Posted April 11, 2019 Author Share Posted April 11, 2019 Thanks for the reply Ken-ji. It looks like if I set eth0 to bridge and put the dockers on that bridge everything works again. I have a 10GB Nic with 2 10GB ports on it that I want all the traffic to go over. That's my br2 bridge. Any idea how I can set that as the primary instead of eth0, which is my 1GB onboard NIC. tower-diagnostics-20190410-1954.zip Quote Link to comment
ken-ji Posted April 11, 2019 Share Posted April 11, 2019 there's the interface rules portion in Settings | Network to renumber the network interfaces But you didn't listen to my initial advice. Do not set two interfaces with the same subnet, unpredictable things happen - like the OS getting confused as to which interface it really should be using to talk to the rest of the world, which normally is ok, but causes issues with Docker and macvlan subinterfaces, which simply put, blocks docker containers with their own IPs from talking to the host on the same subnet. see here for more elaboration: Quote Link to comment
Psycs Posted April 11, 2019 Author Share Posted April 11, 2019 I understood the advice you gave and it made sense. Just wanted to see if the dockers started to communicate once moved to the other interface, which they did. I've got only 1 interface setup now and all is well. Appreciate the help and the docker link. That helped to explain a lot. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.