Skip to content
LatchkeyLatchkey home

docker network ls: List Docker Networks

List the networks Docker knows about.

docker network ls lists all networks, including the built-in bridge, host, and none. This page covers filtering and using it to debug container connectivity.

What it does

docker network ls shows each network ID, name, driver, and scope. The built-in bridge, host, and none always appear; user-defined and compose-created networks show alongside them.

Common usage

Terminal
docker network ls
docker network ls --filter "driver=bridge"
docker network ls --format "{{.Name}} {{.Driver}}"

Common errors in CI

network ls is read-only. The CI use: when containers cannot reach each other, list networks and confirm both joined the same user-defined network with docker inspect. Stale compose networks (project_default) can accumulate on persistent runners; remove them with docker network prune.

Frequently asked questions

docker network ls: List Docker Networks?
docker network ls lists all networks, including the built-in bridge, host, and none. This page covers filtering and using it to debug container connectivity.
What it does?
docker network ls shows each network ID, name, driver, and scope. The built-in bridge, host, and none always appear; user-defined and compose-created networks show alongside them.
Common errors in CI?
network ls is read-only. The CI use: when containers cannot reach each other, list networks and confirm both joined the same user-defined network with docker inspect. Stale compose networks (project_default) can accumulate on persistent runners; remove them with docker network prune.

Related guides

References

Run this faster and cheaper on Latchkey managed runners - self-healing included. Start free → 30-day trial · No credit card