# docker network ls: List Docker Networks

> How docker network ls works: listing networks, the default bridge/host/none, filtering, and debugging connectivity in CI.

Source: https://latchkey.dev/learn/command-reference/docker-network-ls-command  
Updated: 2026-06-25

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.

## FAQ

### 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.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt