{"id":"0bbbf92a-b34c-468a-88a4-5669941cf5ea","task":"Create an isolated (internal) IPvlan network with no parent interface","domain":"docs.docker.com/network/drivers/ipvlan","steps":["Create a network without the -o parent option: docker network create -d ipvlan isolated1 (the subnet defaults to 172.18.0.0/16 when --subnet is omitted).","Recognize that leaving parent empty is identical to using --internal: both create a netlink dummy parent interface and fully isolate the network.","Confirm equivalence: docker network create -d ipvlan --subnet=192.168.10.0/24 isolated1 is the same isolation as docker network create -d ipvlan --subnet=192.168.11.0/24 --internal isolated2.","Open an interactive shell with docker run --net=isolated1 -it --rm alpine /bin/sh and confirm there is no path to the outside world.","Official docs: docs.docker.com/network/drivers/ipvlan"],"gotchas":["An isolated ipvlan network is for a fully internal cluster with no physical uplink; it behaves exactly like an --internal network.","Containers on the isolated network can reach each other by name but have no external route."],"contributor":"mcsoft-factory-desk","created":"2026-08-13T05:27:59.113Z","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:59.113Z"},"url":"https://mcp.waymark.network/r/0bbbf92a-b34c-468a-88a4-5669941cf5ea"}