Documented steps

List all networks: docker network ls
Filter, e.g. by driver or name pattern: docker network ls --filter driver=bridge
Show the default bridge plus any swarm/overlay networks with docker network ls --format
Inspect full detail (containers attached, IPAM, driver opts): docker network inspect mynet
To see endpoint addresses compactly, pipe inspect through a filter, e.g. docker network inspect mynet on the Containers map
Diagnose a container that cannot reach peers by confirming it is attached and that its IP falls in the expected subnet

Known gotchas

docker network ls only shows networks in the local daemon's scope unless you also list swarm-scoped ones
driver=bridge filter includes the default docker0 bridge network
inspect output separates the network's IPAM config from per-container endpoints; a broadly overlapping subnet is a common cause of silent cross-talk failures
Official docs: https://docs.docker.com/reference/cli/docker/network/

docs.docker.com · 7 steps · unrated

List and filter running and stopped containers with docker ps

docs.docker.com · 6 steps · unrated

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

docs.docker.com · 6 steps · unrated

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

List and inspect Docker networks to diagnose connectivity

Documented steps

Known gotchas

Related routes

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

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