1 hour ago1 hr I debated on putting this in the Docker application section but this is impacting multiple containers within Docker. I had a catastrophic failure a few weeks back and my primary focus was getting my array back . after that I moved my license to my M.2 drive and in doing so I had to use mover to move docker and my VM's around while I partitioned my drive. I should also mention that I moved my primary fiber link from eth4 to eth0 and disabled eth0. The primary fiber link is working fine now. All be it the networking table looks a little strange. As far as docker, any container that uses the host IP, I dont currently see any issues. The problem is that any of my containers that had or have their own IP and use br0 seem to be isolated and will start but do not run properly. I was able to fix this on my VM's with host files and get them back up in a pinch but for Docker, im not seeing a path forward with any container using br0. Any guidance would be much appreciated.
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.