A native Cockpit extension for managing Docker Engine on Ubuntu Server. It provides a Portainer-like local interface without deploying another daemon or exposing the Docker socket over TCP.
Current release: 1.3.0
- Container inventory, status, ports, start, stop, logs, inspect, delete
- One-click image updates that safely recreate and restart containers, rolling back if recreation fails
- Direct-download container backups containing an image snapshot, inspection metadata, and named-volume archives
- Restore saved containers from the Containers tab, including their image, configuration, and named-volume data
- Import a complete backup folder from another computer or storage location through the restore dialog
- Create containers with ports, volumes, environment, commands, and restart policies
- Edit and safely recreate containers (the old container is retained until creation succeeds)
- Image, volume, and network inventory and removal
- Docker Compose stack editor, persistence, deploy, stop, and pull support
- YAML installer that accepts pasted Compose YAML or a local
.yaml/.ymlfile - Cockpit privilege escalation; the signed-in administrator must authorize privileged access
- Responsive interface with no external web dependencies
Copy this directory to the server, then run:
chmod +x install.sh
sudo ./install.shOpen https://SERVER-IP:9090, sign in with an Ubuntu administrator account, and select Docker Manager.
The installer targets Ubuntu Server 26.04 LTS and remains compatible with 24.04 LTS. It installs Canonical's cockpit and docker.io packages, preferring docker-compose-v2 and falling back to docker-compose where needed. Existing Docker data is not changed.
For a per-user, uncached Cockpit package during UI development:
mkdir -p ~/.local/share/cockpit
ln -s "$PWD" ~/.local/share/cockpit/docker-managerThe helper must still be installed at /usr/libexec/cockpit-docker-manager/backend.py and executable. Use cockpit-bridge --packages to confirm package discovery.
Docker control is effectively root-level access. The helper uses fixed command shapes, validates stack/container names, never invokes a shell, and requires Cockpit's superuser: require bridge. Restrict Cockpit sign-in to trusted administrators and keep Ubuntu security updates enabled.
Compose files are stored under /etc/cockpit/docker-manager/stacks/<name>/compose.yaml. Uninstalling the extension intentionally preserves this directory.
Container backups stream directly from Docker through Cockpit into a portable ZIP download. The server does not retain a backup archive or backup directory. Only a temporary Docker snapshot image exists during the stream, and it is removed whether the download succeeds or fails. Each ZIP contains container-image.tar, inspect.json, backup.json, and compressed archives for named volumes. Bind-mounted data is not copied because it already resides directly on the host.
Use Containers → Restore backup to restore a saved container. If a container with the same name exists, enable replacement explicitly; this stops and replaces that container and overwrites its named-volume contents with the selected backup. Bind-mounted data is never changed by restore.
To use a downloaded backup, choose Import backup ZIP in the restore dialog. Older timestamped backup folders containing backup.json, inspect.json, container-image.tar, and the optional volumes directory remain supported. Large files are uploaded in chunks and validated before restoration.