Receiving an error message when attempting to create a 2nd MacVLAN Network

Docker Engine Compose
,
1

Currently, I have at least one MacVLAN Network running within Container Manager on my Synology NAS for pihole and unbound. When attempting to create a 2nd MacVLAN Network for adguard, I receive the following error message: "Network adguard_macvlan Creating … Network adguard_macvlan Error … failed to create network adguard_macvlan: Error response from daemon: failed to allocate gateway (192.168.10.1): Address already in use.

My pihole and unbound MacVLAN Network settings:

Subnet 192.168.10.0/24
IP range 192.168.10.200/31
Gateway 192.168.10.1
pihole 192.168.10.200
unbound 192.168.10.201

My attempted adguard MacVLAN Network settings:

Subnet 192.168.10.0/24
IP range 192.168.10.202/32
Gateway 192.168.10.1
adguard 192.168.10.202

My Synology NAS sits on the 192.168.10.0 /24 subnet

Based on the error message, am I not allowed to have multiple MacVLANs pointing to the same Gateway? Basically, for each container I create, I would like a unique IP address instead of using the Synology’s IP address + a port number to access my services.

2

Yep. A gateway ip can only be used by one network, regardless whether it’s a bridge network, macvlan, or ipvlan.

You should consider re-creating your maclan network using a broader ip-range, and use fixed ip’s for each deployed container. I doubt the container manager ui will provide any support for it, but either docker compose or docker run allow configuring a fixed ipv4 address for a container.

3

Thanks. I expanded my ip-range to resolve the issue.