Docker CLI
Docker’s terminal client connects agent commands to containers, images, networks and volumes in the selected environment.
- 6,121 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Docker Engine access can grant host control through containers and mounted host directories.
- Commands target the selected context, which may contain live containers on a remote server.
Install
Manual install
Follow the OS-specific installation guide at https://docs.docker.com/engine/install/. Show `docker context show` and `docker version`. Confirm the environment and allowed operations before managing containers.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Docker Engine access can grant host control through containers and mounted host directories.
- Commands target the selected context, which may contain live containers on a remote server.
This is third-party code. Review the repository files before installing.
What it does
When a containerized app fails, an agent can call Docker CLI to list running containers and read client and server version information. These commands contact Docker Engine, the service that stores images, creates containers and manages their execution. One client can access different environments through Docker contexts. A connection may target the local machine or a remote server. Before building, running or deleting containers, the agent shows the selected environment and planned commands.
Who it is for. Container application teams assigning Docker builds and environment diagnostics to a coding agent.
Good fit when
- A containerized service is unresponsive, so an agent compares running containers with the expected set.
- A team builds an application image from its Dockerfile.
- A developer switches between local Docker and a remote server and checks the active connection.
- A command behaves differently on two machines, and an engineer compares client and Engine versions.
Not a fit when
- The review permits only source inspection without Docker Engine.
- The agent must not receive permission to launch containers in the live environment.
- An unknown image would require access to the whole host.
Example request
Identify the current Docker context and list containers. Ask before building, running or deleting anything.Limitations
The client does not replace Docker Engine: container operations need an accessible daemon or Docker Desktop. Installation varies by OS and distribution, so there is no single universal setup command. A context may target a remote server; a local terminal does not guarantee local execution. Docker access can grant broad capabilities through containers and mounted directories, so an agent needs a defined set of approved operations.
How to disable. Remove Docker CLI from the agent’s allowed tools and revoke its daemon access. Existing containers and stored volumes need separate management.
FAQ
How do I install Docker CLI for my OS?
Select your system in the [Docker Engine installation guide](https://docs.docker.com/engine/install/). Windows and macOS users can follow its Docker Desktop link.
How do I identify the command destination?
Use `docker context show` for the active context and `docker context ls` to list connections. Confirm the target before changing containers.
Where do I start without launching a container?
Run `docker version` for client and server details, then `docker container ls` to list running containers.
What can override the Docker connection?
The `--context` and `--host` options and the `DOCKER_CONTEXT` and `DOCKER_HOST` variables. Check them against `docker context show` before making changes; a local terminal can contact a remote Engine.
Where can I find the available commands?
Run `docker help`. Commands are grouped by containers, images, networks and volumes. The [Docker CLI reference](https://docs.docker.com/reference/cli/docker/) describes each group.
Discussion
No questions or reviews yet.
Related
CLI toolsThe terminal interface presents Docker containers, services and images for user-led investigation with agent assistance.
Container by Aerovato
Container
A CLI for persistent per-project Linux workspaces in Docker or Podman that keep the agent away from the rest of your system
MCP server for managing Docker in natural language: containers, images, networks and volumes, including remote hosts over SSH
dive explores Docker and OCI image layers, highlights file changes and estimates wasted space for inspection or CI checks.
A Docker sandbox for coding agents: a Debian image with Copilot CLI, Codex and Pi, and SSH, RDP and Docker enabled by flags.
Docker Skills
docker-skills
Official Docker skills for agents: Dockerfile and builds, Compose, Sandboxes, Docker Agent and a skill that confirms irreversible actions
README in short
The repository contains client sources and contributor instructions. Source builds use `docker buildx bake`; ordinary installation is documented under Docker Engine.