Docker CLI

Docker CLI is a lightweight, containerized command-line interface for managing Docker containers on your server.

  • Infrastructure
  • Tools & Utilities
Docker CLI is a lightweight, containerized command-line interface for managing Docker containers on your server. It provides an isolated environment for starting, stopping, inspecting, and configuring containers and images via the Docker daemon, making it useful when the host lacks the native CLI or when you prefer a version-pinned, reproducible toolchain.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 1 day ago
Popular
766,142 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
6,142
Open issues
936
Last commit
2026-11-20
License
Apache-2.0
Activity
rising

Checked yesterday - source: GitHub (docker/cli)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Mount Docker socket and use restart=always Start the Autoheal container with --restart=always and mount the Docker socket (Docker's control file) with -v /var/run/docker.sock:/var/run/docker.sock. This keeps the watcher running and gives it permission to restart containers; without the socket, it cannot fix anything. source
  • Label services and add healthchecks Add the autoheal label to each service you want watched, such as autoheal: 'true', and give it a healthcheck; or set AUTOHEAL_CONTAINER_LABEL=all if you want every container checked. Without the label and a healthcheck, Autoheal will not know which containers are allowed to restart or how to tell they are broken. source
  • Add webhook alerts if you want pings Set the WEBHOOK_URL and WEBHOOK_JSON_KEY environment variables for Slack or Discord, or APPRISE_URL for Apprise, to get a message when Autoheal restarts a container. It is optional, but without it you may not notice that a service was unhealthy and was fixed automatically. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I build the Docker CLI from source?

Use Docker and run docker buildx bake to build the CLI. Use docker buildx bake --set binary.platform=linux/arm64 to build for a specific platform.

How do I run the Docker CLI unit tests and full test suite?

Run make -f docker.Makefile test-unit for the unit tests. Run make -f docker.Makefile test for the full test suite.

Where can I find a compact reference for common Docker CLI commands?

The Docker CLI cheat sheet provides quick commands for working with images, containers, and Docker Hub.

Answers sourced from github.com, www.docker.com

Community

Collected 48 days ago - public community threads