May 18, 20242 yr Because of this bug I've had to switch from macvlan to ipvlan. The problem is that I can't reach any of the containers connected with ipvlan. I've tried everything, but I can't figure out what it is. This is the line I use to create the ipvlan: docker network create --driver ipvlan --subnet 192.168.1.0/24 --gateway 192.168.1.1 --opt ipvlan_mode=l2 ipvlan The symptoms: I can start the containers and they show up as having the correct ip addresses and gateway when I do 'docker inspect' in the console. It doesn't matter if I use L3 or L2. It doesn't matter if I specify eth0 as parent or not. The containers won't start at all if I use br0. The containers can ping eachother, but can't ping the outside world, like google.com. I've tried creating the ipvlan in Portainer, but that gives the same result. I've looked everywhere, but every tutorial seems to just have it up and running after creating the container. All I want is that it works as easily as with macvlan. Why is it being so obtuse?
May 18, 20242 yr Community Expert Why are you making your own instead of just changing unraid's docker settings to use it on the network it creates? Edited May 18, 20242 yr by Kilrah
May 18, 20242 yr Community Expert It says right on the page you linked Quote If you are getting call traces related to macvlan, as a first step we recommend navigating to Settings > Docker, switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan. Delete your network first or it'll conflict. Edited May 18, 20242 yr by Kilrah
May 18, 20242 yr Community Expert Shouldn't be the case, delete any ipvlan or macvlan network you may have made yourself first, then make sure it's set to ipvlan in Docker settings and reboot. You'll have to reassign the br0 network to any container that needs it of course. Edited May 18, 20242 yr by Kilrah
May 18, 20242 yr Author I tried that. It doesn't do that. All I have is bridge, host and null. Edited May 18, 20242 yr by BreakfastPurrito
May 18, 20242 yr Author Ok I have solved it. I deleted the entire docker vdisk, rebooted and installed all apps again. Somehow br0 appeared again and is working now.
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.