Docker CLI — Networks Cheat Sheet 2026
Docker CLI Networks Cheat Sheet is the complete quick-reference of Docker CLI Networks commands grouped by function. Copy any command with one click and find what you need with Ctrl+F in under 3 seconds.
Networks
| Action | Command | Useful flags |
|---|---|---|
| List all available and configured networks on Docker daemon |
|
|
| Create a user-defined network |
|
--driver |
| Display detailed information about one or more networks |
|
|
| Connect a container to a network using a name or ID |
|
|
| Disconnect a container from a network |
|
|
| Remove all unused (not referenced by any container) networks |
|
|
| Remove one or more unused networks |
|
|
⚠️ Dangerous / Destructive Commands
These commands are irreversible. Verify your environment (dev/staging vs prod) before running them.
| Action | Command | Warning |
|---|---|---|
| ⚠️ Destroy ⚠️ |
|
Irreversible — verify the target before running |
| ⚠️ Delete |
|
Irreversible — verify the target before running |
| ⚠️ Prune ⚠️ |
|
Irreversible — verify the target before running |
| ⚠️ Delete |
|
Irreversible — verify the target before running |
| ⚠️ Delete |
|
Irreversible — verify the target before running |
FAQ — Frequently Asked Questions
What is the difference between Networks and the other groups?
Each group in this Docker CLI cheat sheet covers a distinct area. Networks focuses on its specific scope, while the other groups and the remaining groups cover networking, storage, security and diagnostics respectively.
How do I check the installed Docker CLI version?
Run the version command (usually docker version or docker --version). The output shows the client and, when applicable, the server version.
Why does Docker CLI return ‘permission denied’?
A ‘permission denied’ error in Docker CLI usually means the current user lacks sufficient privileges or credentials are not configured. Check: (1) assigned IAM/RBAC roles, (2) an active authentication context via the corresponding login command.
How do I filter Docker CLI output by status or name?
Use flags such as --filter, --selector or --query depending on the tool. You can also pipe into grep or jq to process JSON:
docker list | grep RUNNING
What is the fastest way to debug a Docker CLI error?
Add the verbose flag (--verbose, -v or --debug) to the failing command. This reveals the underlying HTTP/API calls and the full error response body.
Official sources & references
Commands cross-checked against vendor documentation and high-authority repositories: