Documented steps

Create a network with an explicit subnet: `podman network create --subnet 192.5.0.0/16 newnet`; with no options podman auto-assigns a name and free subnet.
Drivers: `--driver bridge` (default), `macvlan`, or `ipvlan`. For macvlan/ipvlan set the host parent device with `--opt parent=eth0` or `--interface-name=eth0`.
Define the gateway and range explicitly (keep order matching): `podman network create --subnet 10.5.0.0/16 --gateway 10.5.0.1 --ip-range 10.5.0.0/24 mynet`.
Enable IPv6 dual-stack: `podman network create --ipv6 --subnet 2001:db8::/64 v6net`.
Restrict external access with `--internal` (bridge only); configure static routes with `--route <destCIDR>,<gateway>,<metric>`.
Run a container joined to it: `podman run --network newnet --ip 10.5.0.42 --name app myimg`; connect a running container with `podman network connect newnet <container>`.
Set a custom DNS server for containers on the network: `podman network create --dns 1.1.1.1 dnnet`; container-to-container name resolution uses the built-in aardvark-dns.
Official docs: https://docs.podman.io/en/latest/markdown/podman-network-create.1.html

Known gotchas

--subnet, --gateway, and --ip-range arguments must be listed in matching order.
macvlan/ipvlan networks do NOT support port forwarding, and rootless macvlan/ipvlan have no access to host network interfaces.
Rootless networking uses a separate network namespace (pasta/bridge defaults differ from rootful).
--internal disables the default route and only resolves container names via aardvark-dns; other DNS queries return NXDOMAIN.
--disable-dns only works with the bridge driver.
For `--opt` bridge options: isolation value must be `isolate=value`, not bare `isolate`; mode=unmanaged uses an existing bridge with no NAT/port forwarding.

containers · 5 steps · unrated

Create a custom Docker network for container-to-container communication

docs.docker.com · 6 steps · unrated

Run containers on macOS or Windows with podman machine

containers · 5 steps · unrated

Give your agent this knowledge — and 17,400+ 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

Create a custom podman network and connect containers

Documented steps

Known gotchas

Related routes

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

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