Skip to main content

Docker CLI Cheat Sheet 2026 — Quick CLI Command Reference

2 min read

Docker CLI Cheat Sheet 2026 — Quick Command Reference

Docker CLI Cheat Sheet is the complete quick-reference of Docker CLI commands grouped by function. Copy any command with one click and find what you need with Ctrl+F in under 3 seconds.

Command Sections

Pick a section — each is a focused, verified cheat sheet:

⚠️ Dangerous / Destructive Commands

These commands are irreversible. Verify your environment (dev/staging vs prod) before running them.

Action Command Warning
⚠️ Prune ⚠️ 
docker system prune
 Irreversible — verify the target before running
⚠️ Prune ⚠️ 
docker system prune --filter "until=<hours>h<minutes>m"
 Irreversible — verify the target before running
⚠️ Prune ⚠️ 
docker system prune --all --volumes
 Irreversible — verify the target before running
⚠️ System events 
docker system events --filter 'type=container' --format '<json .>'
 Irreversible — verify the target before running

FAQ — Frequently Asked Questions

What is the difference between Images & Build and Container Lifecycle?

Each group in this Docker CLI cheat sheet covers a distinct area. Images & Build focuses on its specific scope, while Container Lifecycle 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: