dockly CLI
The terminal interface presents Docker containers, services and images for user-led investigation with agent assistance.
- 4,036 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Docker daemon access enables container and host-environment management; filtering the list does not reduce those privileges.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/docklyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Docker daemon access enables container and host-environment management; filtering the list does not reduce those privileges.
This is third-party code. Review the repository files before installing.
What it does
dockly opens a terminal interface for Docker management. It connects to the local daemon through a Unix socket and displays containers, services and images. Users can inspect the environment while an agent explains state and plans actions. Host, port and protocol options support other daemons. Container filters focus the display on a test project; they do not create a separate Docker permission boundary.
Who it is for. Docker operators needing an interactive terminal overview on a local or authorized remote host.
Good fit when
- A test machine needs a quick container and image overview.
- SSH administration lacks a browser dashboard.
- Agent-assisted diagnosis should focus on project containers.
- A specific Docker daemon needs an explicitly configured connection.
Not a fit when
- The process must not access the Docker socket.
- A display filter must enforce isolation from other containers.
- The agent needs a fully non-interactive output format.
Example request
Prepare dockly for the test Docker host and show connection settings and the container filter before management actions.Limitations
Access to a running Docker daemon is required; verify the socket or remote endpoint before starting. Node.js must meet the selected dockly release’s requirements; check its `engines` field before installation or updates. Permissions come from the Docker connection, while container filters only narrow the visible list. Rendering depends on terminal capabilities and locale; fix garbled symbols before managing production containers.
How to disable. Close dockly and remove unused remote access. Closing the interface does not remove containers or images.
FAQ
How do I start locally?
`dockly` uses the local Docker socket by default.
Can I choose a different socket?
Yes. Use `--socketPath`.
How do I select a remote host?
Set `--host`, `--port` and the supported `--protocol` for your connection.
How do I show only test containers?
Configure `--containerFilters` by container name or status.
Why are symbols garbled?
Check terminal support and a UTF-8 locale in `LANG` and `LC_ALL`.
Discussion
No questions or reviews yet.
Related
CLI toolsDocker’s terminal client connects agent commands to containers, images, networks and volumes in the selected environment.
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
dive explores Docker and OCI image layers, highlights file changes and estimates wasted space for inspection or CI checks.
MCP server for managing Docker in natural language: containers, images, networks and volumes, including remote hosts over SSH
nerdctl controls containerd with Docker-like commands for containers and images, including Compose and optional BuildKit builds.
A Docker sandbox for coding agents: a Debian image with Copilot CLI, Codex and Pi, and SSH, RDP and Docker enabled by flags.
README in short
The interface can itself run in a container with the Docker socket mounted. That still exposes the host daemon.