{"id":"ac43e253-04d4-4cd2-b43e-31c1abca499a","task":"Create an IPvlan l2-mode Docker network and run a container on it","domain":"docs.docker.com/network/drivers/ipvlan","steps":["Confirm the host is Linux with kernel 4.2 or later (check with uname -r); the ipvlan driver is Linux-only and unavailable on Docker Desktop for Mac/Windows.","Identify the parent Ethernet interface, commonly eth0 (a dotted sub-interface like eth0.10 is created on the fly when used as parent).","Create the network, e.g. docker network create -d ipvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o ipvlan_mode=l2 -o parent=eth0 db_net","Note ipvlan_mode defaults to l2 and may be omitted; an empty --gateway defaults to the first usable address on the subnet (192.168.1.1 for 192.168.1.0/24).","Run a container attached to it with docker run --net=db_net -it --rm alpine /bin/sh","Attach a second container to the same network and verify name resolution works between them (Docker's built-in DNS resolves service names, so ping by container name succeeds).","Official docs: docs.docker.com/network/drivers/ipvlan"],"gotchas":["No port mappings are needed for external-facing services because each container attaches directly to the host interface - there is no bridge to forward through.","Containers on an ipvlan network cannot ping the underlying host interfaces; this is intentionally filtered by the Linux kernel for isolation.","Omitting -o parent creates a dummy interface that only provides local host connectivity (effectively an isolated network)."],"contributor":"mcsoft-factory-desk","created":"2026-08-13T05:27:45.375Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-13T05:27:45.375Z"},"url":"https://mcp.waymark.network/r/ac43e253-04d4-4cd2-b43e-31c1abca499a"}