Newv1.119.0: Backups on the minute, a dashboard on one screen, and an icon that fills its tile12 October 2026

The everyday work of Docker Desktop. Without Docker Desktop.

A lightweight desktop client for any Docker daemon. Containers, images, volumes, networks, compose and logs in one fast window. Built for Docker in WSL, happy with any daemon you can reach.

$ npx docker-client-mx

Linux AppImage · Windows on ARM · macOS via npm · Node 20+ · Version 1.119.0

Works with any Docker daemonWindows · Linux · macOS

The Docker Client MX containers page on a home server: the compose projects caddy, forgejo-runner, infra and recept-snatcher as groups, and per container its image, IP address, ports and live CPU and memory.
No more typingdocker ps
Built with
  • Angular
  • Electron
  • TypeScript
  • Node.js
  • MIT licensed
Works with
  • Docker Engine
  • Docker in WSL
  • Docker over SSH
  • Docker Desktop
  • Swarm
  • Compose

Principles

A / CLIENT, NOT ENGINE

Talks to your daemon. Doesn’t replace it.

Docker Client MX never installs or manages the engine. It finds your daemon the same way the Docker CLI does and gets to work.

B / MADE FOR WSL

Docker in WSL, with a proper window on it.

Designed around Docker running inside WSL on Windows. Switch Docker contexts straight from the status bar when you need another host.

C / KEYBOARD FIRST

Everything is one Ctrl+K away.

A command palette for every page and action. Cmd+K on macOS. Your mouse can take the afternoon off.

Everything you open Docker Desktop for.

Nineteen pages, one window. Each one does the job you came for, then gets out of the way. Or see everything it does on one list ↓

01

Dashboard →

Engine status, CPU, memory and network charts, disk usage, a prune dialog, and what needs attention before it goes wrong.

02

Containers →

Grouped by compose project, with bulk start, stop, restart and remove. Live logs, a terminal, a file browser and one-click diagnosis on every container.

03

Images →

Pull with per-layer progress, run a container from an image, see newer versions by patch, minor and major with their release notes, scan for known vulnerabilities, and recreate compose containers.

04

Volumes & networks →

List, remove and prune. Look inside a volume and change its files, copy it, and see who uses it. Rename a network, and find every port on one page.

05

Backups →

A volume on a schedule at a fixed time, checked after writing, encrypted with your password and sent to SFTP, S3 or WebDAV. For a database, its own dump. Checked again before it restores, as a whole or only the files you pick, also a whole compose project.

06

Compose →

Bring whole projects up or down together, as one group, see one as a diagram, check its resilience, and take one to your own server. Turn a docker run command into a compose file, or deploy one from a git repository.

07

Catalog →

Ready-made compose projects from Arcane, Portainer or a list of your own: fill in a few fields, see what each asks of your engine, and deploy it. Your own projects become templates to share.

08

Unified logs →

The logs of all running containers merged into one view, with a level filter and filters you save under a name.

09

Terminals →

A root shell on the Docker host, next to a shell inside any container, and a cheat sheet that puts a Docker command on its prompt.

10

Claude →

A Claude tab on every container and on the host terminal, with Claude or your own model. It reads logs, events, stats and inspect data and suggests a fix, and acts only if you let it.

11

AI →

Claude or a model on your own machine. It suggests until you let it act within your rules, helps when a build fails, and lets Claude Code in through an MCP endpoint.

12

Command palette →

Ctrl+K jumps to any page or container and runs the actions on it. Type an instruction in plain words — the simple ones the app understands by itself.

13

Connections →

Docker in WSL, a server over SSH, or Docker Desktop. Switch machines from the status bar, and see them all on one page.

14

WSL →

Docker in WSL without Docker Desktop: move over in one wizard, the .wslconfig with a preview, a disk file that shrinks, ports for your network, DOCKER_HOST for Windows, and WSL after sleep.

15

Swarm →

Services per stack, nodes, secrets and configs on a manager. Scale, roll out and roll back, deploy stacks from their compose file, and start or join a swarm on your own servers.

16

Checkup & reports →

One page that checks your setup against thirty-two rules and links to the fix for each, also on a schedule over every machine you follow. Plus a report of what runs on a machine, yours or another, as Markdown or HTML.

17

History →

The notifications you missed, a day of CPU and memory per container, and one page with everything the engine reported.

18

Updates →

New images on a moment you pick, per project, also to a newer patch or minor, the database before the app. The app waits to see the container come back and puts the old image back if it does not.

19

Background mode →

Runs in the system tray, notifies you when a container crashes, becomes unhealthy, hits its memory limit or sets off one of your own rules, also on your phone if you like, and can start at login. In English, Dutch, German, French or Spanish, light or dark.

All 281 things it does, on one list.

Every feature page, boiled down to one line per thing it can do. Each line opens its tile on that page, with the whole story.

281 things on 19 pages.

Optional · bring your own key, or your own model

A container fell over? Ask Claude why.

The Claude tab helps you troubleshoot with the context of your containers and logs at hand. It is entirely optional and uses your own Anthropic API key, or a model on your own machine such as Ollama. It suggests, and acts only if you let it. Leave it off and nothing leaves your machine.

Off by defaultYour own API key or modelSuggests until you say otherwise

Up and running in a minute.

Pick the way that suits your machine. All three talk to the daemon you already have.

WINDOWS · LINUX

Installer

The Setup.exe for Windows, with a build of its own for ARM processors, or an AppImage for Linux on x86_64: make it executable and start it. All of them keep themselves up to date.

ANY PLATFORM

npm

Run it straight away with npx, or install it globally. Needs Node 20 or newer.

$ npx docker-client-mx
$ npm i -g docker-client-mx
CONTRIBUTORS

From source

Clone the repository and run the development build.

$ git clone https://codeberg.org/MartijnSchimmel/docker-client-mx.git
$ npm install
$ npm run dev
You’ll need
A running Docker daemon.Found automatically, like the Docker CLI does.
Docker CLI + compose plugin.Only for compose operations.
A Claude API key, or a local model.Optional, only for the Claude tab and the AI features.