Overview

Docker Manager runs the stacks and containers on all your servers from one web page. You deploy and edit stacks, edit their files, read logs, open terminals, update images and back everything up, without SSH.

What you can do

Stacks

Create, deploy and edit stacks, or import the Compose projects you already run.

Containers, images, volumes, networks

See and control everything Docker runs on every server.

File Manager

Edit, upload and download files of stacks and volumes in the browser.

Logs and Terminal

Read live logs and open a shell in any container.

Updates

Find newer images and update your stacks and containers, by hand or on a schedule.

Backups

Back up your stacks, volumes and Docker Manager itself, and restore them.

Migrations

Move a stack, a volume or a whole server to another server.

Monitoring

Watch the health of every server's disks and RAID arrays.

Users and permissions

Invite people and decide what each of them may see and do.

It works on phones too: lists become cards, the actions you use most sit at the bottom of the screen, and Back closes what is open over the page, such as a dialog, Filters or search.

How it works

Docker Manager has two parts:

Docker Manager is the web app. You run it once, on one server.
The Docker Agent is a small container on every server you manage. It connects out to Docker Manager and does the work on its server. It opens no ports, so servers need no firewall changes.

Each server with its agent is an environment. The environment switcher at the top of the side menu picks which one the pages show, or All Environments.

Longer tasks, such as a deploy or a backup, run as jobs and keep running when you close the browser:

Jobs in the menu lists them all, with why a job failed. Each row's menu (⋯) offers Try Again for a failed job and Cancel Job for a running one you may cancel.
View Jobs lists only the jobs of one stack (in its More Stack Actions menu), or of a container, image, volume or network (in its More Actions menu).
When a job fails, its message offers Open Job, and View Logs when a container didn't start.
A job you started that fails while Docker Manager isn't open shows in the bell the next time you open it, with a message linking to it.

If you leave a page or close a dialog with unsaved changes, or before you press Done on a link or code shown only once, Docker Manager asks first; Keep Editing takes you back.

Backups, update checks, updates and cleanups can run on a schedule: hourly, daily, weekly or with a cron expression, in the time zone you pick. Nothing runs on its own until you turn its schedule on. Schedules in the menu lists them all.

Press Ctrl K (⌘ K on a Mac) to jump to any page, stack or container.

What you need

A Linux server with a 64-bit Intel or AMD (amd64) or ARM (arm64) processor.
Docker Engine 25.0 or newer with the Compose plugin.
A domain name, such as docker.example.com, and a reverse proxy that serves it over HTTPS. Docker Manager does not work over plain HTTP.

Docker Desktop, rootless Docker, the Docker built into NAS systems and Docker Swarm are not supported.

Protect your sign-in

The agent has full control of Docker, and so of the whole server. Anyone who can sign in with enough permissions can do the same. Use a strong password and two-factor sign-in (see Users & Groups).

Ready? Follow the Quickstart.