Please help me with a macvlan

General
13

I hear you. I tried it, and these are the results with docker-ce 28.0.1:

Comma separated ips, instead of cidr?

me@host~ # docker network create -d macvlan \
    --subnet=192.168.200.0/24 \
    --gateway=192.168.200.1 \
    --ip-range=192.168.200.100,192.168.200.101 \
    -o parent=eth0 \
    macvlan0
every ip-range or gateway must have a corresponding subnet

result: error → no network created

ip range starts with ip of the cidr?

me@host ~ # docker network create -d macvlan \
    --subnet=192.168.200.0/24 \
    --gateway=192.168.200.1 \
    --ip-range=192.168.200.100/28 \
    -o parent=eth0 \
    macvlan0
Error response from daemon: invalid network config:
invalid ip-range 192.168.200.100/28: it should be 192.168.200.96/28

result: error → no network created

With docker-ce 24.0.2

Comma separated ips, instead of cidr?

me@host:~# docker network create -d macvlan \
>     --subnet=192.168.200.0/24 \
>     --gateway=192.168.200.1 \
>     --ip-range=192.168.200.100,192.168.200.101 \
>     -o parent=eth0 \
>     macvlan0
every ip-range or gateway must have a corresponding subnet

result: error → no network created

ip range starts with ip of the cidr?

me@host:~# docker network create -d macvlan   \
  --subnet=192.168.200.0/24 \
  --gateway=192.168.200.1  \
  --ip-range=192.168.200.100/28  \
   -o parent=eth0  \
   macvlan0
2be397cc54ede6422b436932aa62b116c58389ff44d6af2a2ca14266dd670912

me@host:~# docker run -ti --rm --network macvlan0 alpine ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1
    link/sit 0.0.0.0 brd 0.0.0.0
37: eth0@sit0: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 02:42:c0:a8:c8:60 brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.96/24 brd 192.168.200.255 scope global eth0
       valid_lft forever preferred_lft forever

result: network can be created, container still has ip 192.168.200.96.

I am not able to verify either one of the claims.