April 10, 20251 yr Hi all, I've encountered a problem with my dockers. Recently noticed one of my docker containers no longer starts due to an IP conflict. I don't have anything else using that IP so looked further in to it. When I inspect my custom br0.6 (VLAN6) network, I see the following; root@unraid:~# docker network inspect br0.6 [ { "Name": "br0.6", "Id": "c4d01ec67b5eb12d47f691fac81955192b0ec33116cc972ab70b24196844dac8", "Created": "2025-04-09T19:55:27.753465705+01:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.6.0/24", "Gateway": "192.168.6.1", "AuxiliaryAddresses": { "server": "192.168.6.5" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" The docker container that won't start is at 192.168.6.5, and surely enough I see this IP under the custom network config. I've tried removing the custom docker network and completely disabling VLANs, and then setting up from scratch but it keeps coming back. Where is this "server: IP" coming from? I can change my docker container IP to something different, and it works, but this is really bugging me. Anyone know how to remove this from the config? Edited April 10, 20251 yr by chrisgtl spelling
April 10, 20251 yr afaik auxiliary adresse should be the address of your unraid server interface in vlan6. Obviously you can't give that address to container. edit: auxiliary address is normally used exclude ip from docker dhcp. I don't use it as i always assign containers addresses manually. So if you want use this address for your docker container you first have disable ip assignement for your eth0.6 subinterface. I suppose you'll have to delete and recreate your network. Edited April 10, 20251 yr by caplam
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.