Running Docker on a server usually means an SSH session and a long list of commands. docker ps to see what is alive, docker logs in a second window, docker exec -it to get a shell, and docker compose from the right folder. Every check is a command, and one wrong docker rm can take your data with it.
The Docker tab replaces that. Connect to a server and everything Docker runs there is on screen, with buttons for what you would normally type. CtrlOps sends the Docker commands over your SSH connection, so the server needs no agent and no panel. For an overview of Docker Management, including what it costs and how it compares, see the feature page.
The tabs inside Docker
Each server has its own Docker page, so everything here belongs to the server you are connected to.
| Tab | What it is for |
|---|---|
| Containers | The apps that run on this server. Start, stop, open a terminal, and create new ones |
| Dashboard | The health of the server at a glance, Quick Actions, and clean-up |
| Images | The templates a container starts from. Pull, build, run, or delete them |
| Volumes | Storage that stays after you remove a container, and its backups |
| Networks | How containers reach each other and the outside |
| Logs | Pick a container and read its output live |
| Domains | Hostnames routed to this server, with their certificate status |
Why a Docker tab instead of docker commands
| Doing it by hand | Doing it in CtrlOps |
|---|---|
ssh user@host, then docker ps -a | Click the server, click Docker |
docker logs -f <name> | Click Logs on the row |
docker exec -it <name> sh | Click the container. It opens on Terminal |
docker run -d -p 8080:80 ... | Create → Application |
docker compose up -d | Compose Up on the stack |
docker pull | Pull Image in Images |
docker system prune | Prune System in Dashboard, with a preview first |
Before you start
Your plan. Docker is a paid add-on on the Personal and Team plans. It is included in Enterprise, in every Lifetime plan, and in the 14-day free trial. It is not on the Free plan. On a plan without Docker, the tab shows Docker is not included in your current plan with an Upgrade button. See pricing for what the add-on costs.
Your login on the server. CtrlOps checks this when you connect.
| Login | What you see |
|---|---|
root | The full Docker tab |
| Sudo, no password needed | The full Docker tab |
| Sudo, password needed | Docker needs sudo. Type the password once, and the full tab opens |
Sudo rights and in the docker group | The full tab. CtrlOps asks for the password only to install, start, or restart Docker |
Standard user, in the docker group or not | Locked: Docker needs root or sudo access. |
| Restricted | The Docker item is locked in the sidebar |
The sudo password stays in memory for that tab only, and it is never written to disk or into a command. Tick Remember password on this device to save it encrypted on your computer for this server.
Your server.
- It must run Linux, with Docker Engine 20.10 or later. An older version works, but it shows the warning Docker is too old.
- If Docker is missing, CtrlOps can install it on servers that use apt, dnf, yum, zypper, apk, or pacman.
- Compose stacks need Docker Compose v2. Deploying a new stack from CtrlOps needs version 2.20 or later.
- Podman, rootless Docker, and servers that are not Linux are not supported. The tab shows This Docker setup is not supported in v1.
- Docker installed from snap works with limits: Stacks, Compose, Build, and bind mounts outside your home folder are off.
Open the Docker tab
Connect to your server
Open CtrlOps and click the server you want to manage.
Click Docker
In the left sidebar, click Docker. It sits right under AI Terminal, and it opens on the Containers tab.
Install Docker if it is missing
If the server has no Docker, the tab shows Docker Engine not installed.
Click Install Docker
Check what will change, then click Install
Before anything runs, a window shows what CtrlOps will do on this server.
| Row | What it tells you |
|---|---|
| OS | The server's operating system |
| Docker version | The version it installs, and what it installs instead if the server can't use the Docker repository |
| Time | About 2 to 5 minutes |
| Changes | The Docker packages, docker.service starting when the server starts, and log limits in /etc/docker/daemon.json (10 MB and 3 files for each container) |
To see the exact commands, click Show commands. Then click Install, or Cancel to leave the server as it is.
Each step shows as it runs. See Install Docker on a server for the details.
The chip at the right of the tabs shows the Docker Engine state and version: Engine healthy, Engine stopped, or Engine starts.
What the Docker tab does not do
- Kubernetes: not supported.
- Docker Swarm: CtrlOps does not manage Swarm. A Swarm stack shows in the list, but it is read-only. The only link to Swarm is in Networks, where an overlay network can start Swarm mode after you confirm.
- Container alerts: it shows the state of each container as it is now, and it does not send alerts. For the CPU, memory, and disk of the server, use Alerts.
- Metrics history: CPU and memory are live. There is no long-term history.
- All servers in one list: each server has its own Docker page.
- Docker on your own computer: CtrlOps manages Docker on Linux servers that you reach over SSH.
- The Deployments tab: Deployments stays for Node.js, React, and Next.js apps. Docker builds live here.
How Docker works on your server
CtrlOps runs the docker command over SSH, on its own SSH connection, so slow Docker work does not hold up PM2 or the File Manager. Long jobs such as an install, a pull, a build, or a deploy run on the server by themselves. If SSH drops or you close the app, the job keeps going, and CtrlOps picks it up when you connect again.
There is no agent or panel on the server. A few actions change the server when you use them:
| Action | What it changes |
|---|---|
| Install Docker | Adds the Docker packages, starts docker.service when the server starts, and adds log limits to /etc/docker/daemon.json (10 MB and 3 files for each container) |
| Deploy a stack | Makes the stack folder with the compose file and a private .env file |
| Sign in to a registry | Docker saves the login in ~/.docker/config.json on the server |
| Domains | Add Nginx and Certbot or a Traefik container, and can open ports 80 and 443 in the firewall if you choose |
| Volume backups | Add a scheduled job and the backup settings on the server |
| Long jobs | Keep a small job folder with the log. CtrlOps removes it 24 hours after the job ends |
Run the Security Audit to check your Docker setup. It includes Docker checks.
Troubleshooting
Most failures in the Docker tab show Show details with the Likely cause, Retry where it helps, and Copy report. Send that report with any support question. For problems with a container or a stack, see Containers.
Docker needs root or sudo access.
Your login on this server has the Standard role, and only root and sudo accounts can use Docker in CtrlOps. Being in the docker group does not change this. Connect with a login that has sudo rights, or ask an administrator to give yours sudo.
Docker needs sudo.
Your login has sudo rights, but CtrlOps needs the password. Type it and click Continue. If the message is The sudo password did not work., type it again. If you saved a password and it stopped working, CtrlOps deletes it and asks again.
This account has no sudo rights on this server.
The login is not allowed to use sudo. Connect with a different login, or ask an administrator. If the message is This server has no sudo command. Connect as root., the server has no sudo at all, so connect as root.
Docker is not included in your current plan
Docker is not on the Free plan, and it is a paid add-on on Personal and Team. Click Upgrade, or see pricing.
This Docker setup is not supported in v1.
The reason shows below the title. The server runs Podman in place of Docker, runs Docker in rootless mode, or is not Linux. CtrlOps works with the normal system Docker Engine on Linux.
Docker Engine stopped.
Docker is installed but not running. Click Start Docker. If you see The Docker Engine did not start in 60 seconds., the last lines of its log show below the message. If your login has no sudo, the tab shows a command for an administrator to run.
Could not read the Docker state.
CtrlOps could not get an answer from the server. Click Retry. Open Show details to see the likely cause, such as a dropped SSH connection or a Docker Engine that does not answer.
This account cannot use the Docker socket.
The login has no permission on the Docker socket. Connect with an account that has sudo, or ask an administrator.
CtrlOps cannot answer this sudo prompt.
Your server asks for more than a password at sudo, such as a one-time code. CtrlOps cannot answer that for live logs and the terminal. Use NOPASSWD sudo or the docker group for this login.
Frequently Asked Questions
Who can use the Docker tab in CtrlOps?
Only logins with root or sudo rights on the server. A Standard user sees Docker needs root or sudo access. even if the login is in the docker group, and a Restricted login sees the Docker item locked in the sidebar. A sudo login that needs a password is asked for it the first time.
Which plans include Docker?
Docker is a paid add-on on the Personal and Team plans. It is included in Enterprise, in every Lifetime plan, and in the 14-day free trial. It is not on the Free plan.
Does CtrlOps install an agent on my server for Docker?
No. CtrlOps sends Docker commands over your SSH connection, so there is no agent and no panel on the server. A few features change the server when you use them, for example Install Docker adds the Docker packages and a Compose deploy makes a stack folder.
Which servers does the Docker tab work on?
Linux servers with Docker Engine 20.10 or later. If Docker is missing, CtrlOps can install it on servers that use apt, dnf, yum, zypper, apk, or pacman. Podman, rootless Docker, and servers that are not Linux are not supported, and Docker from snap has limits.
Does CtrlOps support Kubernetes or Docker Swarm?
No. CtrlOps manages Docker Engine and Docker Compose on each server. It does not manage Kubernetes or Swarm. A Swarm stack shows in the list, but it is read-only.
Will CtrlOps alert me when a container stops?
No. The Docker tab shows the state of each container as it is now, and it does not send container alerts. Alerts for the CPU, memory, and disk of the server are in the Alerts tab.
Can I see the containers of all my servers in one list?
No. Each server has its own Docker page, so you see the containers of one server at a time. To work on several servers, open each one in its own tab.
