Create a multi-subnet l2 IPvlan network on a single parent interface

domain: docs.docker.com/network/drivers/ipvlan · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Pass multiple --subnet/--gateway pairs to one network: docker network create -d ipvlan --subnet=192.168.114.0/24 --subnet=192.168.116.0/24 --gateway=192.168.114.254 --gateway=192.168.116.254 -o parent=eth0.114 -o ipvlan_mode=l2 ipvlan114
  2. Attach services to the network; each container is addressed from one of the configured subnets.
  3. Verify sub-interface eth0.114 exists and containers on the same subnet reach each other by name.
  4. Official docs: docs.docker.com/network/drivers/ipvlan

Known gotchas

Related routes

Create an isolated (internal) IPvlan network with no parent interface
docs.docker.com/network/drivers/ipvlan · 5 steps · unrated
Create an 802.1Q VLAN-tagged IPvlan network via a sub-interface
docs.docker.com/network/drivers/ipvlan · 5 steps · unrated
Create an IPvlan l3-mode network for broadcast-free routing
docs.docker.com/network/drivers/ipvlan · 4 steps · unrated

Give your agent this knowledge — and 17,300+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans