Features04 Volumes & networks

Your data and your wiring, in plain sight.

Look inside a volume and change what is in it, copy it, back it up and restore it. See which containers use a volume or are attached to a network, rename a network, and find every port on one page, also the ones taken outside Docker.

What is a volume, really?Read the comic: a pantry that stays full while the cooks come and go →
Fig. — Volumes, with the actions of one volume.

What you can do

Create by hand

Make a volume or a network without writing a compose file, with subnet and gateway under Advanced.

Look inside a volume

Browse its files, edit a text file, upload, rename or remove, and download a single file. Browsing itself stays read-only.

Back up and restore

By hand or on a schedule, encrypted, to another server or as a dump of the database, and back in three ways. The next page, Backups, has the whole story.

Copy a volume

Into a new volume, with owners and permissions kept.

A volume as an image

Save a volume as an image, with its content, owners and permissions, and push it with the registries you already use. On another machine, pull it and make a new volume from it; an existing volume is never overwritten.

Who uses a volume

The In use column names the containers, each a link to its page. The menu shows every container that has it, running or stopped, with the path inside it and whether it is read-only. That is what tells you what an unnamed volume is.

Remove and prune

Clear out what nothing uses any more.

Who is on a network

Every network with its subnet and gateway, and the containers on it by name, each a link; connect or disconnect one. The networks of a swarm say so: ingress, docker_gwbridge, and an overlay network with the services that use it, so the unused count is what Docker would remove.

Rename a network

Docker cannot, so the app creates it again under the new name with the same subnet and moves everything across, compose projects and swarm services included.

All ports on one page

Every published port with its address, searchable like the lists (several words, !word, /regex/), including the ones that went missing, and what else listens on the machine. A switch hides the ports outside Docker.

Ports

Which container is on port 3000? And what else is listening?

The Ports page, under Networks, lists every published port with its address and container, and between them what listens on the machine outside Docker: sshd, Samba, a DNS resolver, or a database of the server itself. For those it says where to see which program it is. Search for a port number and you have the answer: a container, outside Docker, or free. A published port opens in the browser on the machine it is on, also when that is a server. With Docker Desktop the machine is its VM, and the page says that ports on your own computer are not in the list.

Fig. — Ports on a server: containers, and between them what listens outside Docker.

Networks

A network by another name.

Docker has no rename for a network. The app creates it again under the new name, with the same driver, options and subnet, and moves everything on it across. A container that has it as its main network is recreated exactly as it was: ports with their address, anonymous volumes, alias and fixed IP. Compose knows a network by name, so the dialog gives the lines for the compose file and waits until compose config sees the new name; then compose recreates its services. Swarm services let go of the network and get the new one, and the app waits until their tasks run again. If the old network cannot be replaced, everything goes back as it was.

Fig. — Renaming recept-snatcher: Docker cannot rename a network, so the app recreates it and moves everything across.

All features

Try it on your own daemon.
Free and open source. Windows installer, Linux AppImage, or npx on any platform.
Download for Windows
$ npx docker-client-mx