Images, volumes and networks

i on the container list opens the server’s images, volumes and networks, in three tabs. Each is a table with the biggest first.

 ▲ laraport › Production › Images, volumes, networks                             ● ssh shop.example.com 1 Images  2 Volumes  3 Networks            Images · 7 · 2 update(s) available  image                      id        size   unique  created       used by         update        shop/app:2026.11.3         4f1c2a9e  612MB  48MB    3 days ago    3 container(s)  local build   shop/app:2026.10.28        9b7e01d2  608MB  44MB    9 days ago    unused          local build   postgres:17                c0ffee17  438MB          5 weeks ago   1 container(s)  update avai…  redis:7-alpine             7ed15a1b  41MB           2 months ago  1 container(s)  up to date    getmeili/meilisearch:v1.8  5e1a3b88  142MB          6 months ago  1 container(s)  up to date    php:8.2-cli                a2b3c4d5  498MB          8 months ago  1 container(s)  update avai…  <none> (dangling)          e9d8c7b6  603MB          3 weeks ago   unused          NULL          7 rows  ·  row 1 · col 1/7 image LARAPORT  Production  tab/1-3 images · volumes · networks  ↑↓ move  D remove  P prune unused    ? help 

Tab	Shows
Images	Name, ID, size, unique size, age, and how many containers use it. Untagged images are marked dangling
Volumes	Name, Compose project, size, how many containers use it, driver
Networks	Name, ID, driver, scope, attached containers, internal

Cleaning up

Key	Action
D	Remove the selected item. A tagged image is removed by name, so only that tag goes
P	Remove the unused items of the tab
A	Remove every unused image, tagged or not
r	Reload

Every removal shows its docker command first. The confirmation says when the item is in use, and that a volume’s data is deleted for good. Docker’s own networks (bridge, host, none, ingress) cannot be removed.

Image updates

u on the Images tab asks each image’s registry for the current digest of its tag and compares it with the one the image was pulled with. Nothing is downloaded. The update column then says:

• up to date;
• update available;
• local build: built on the server, nothing to compare with;
• can't check, with the reason: the registry’s rate limit, no access to a private image, or no docker buildx on the server. See Troubleshooting.

p pulls the selected image. Running containers keep the old image until they are recreated, for example by a redeploy in Dokploy or Coolify.

Server cleanup

g on the container list offers the classic commands: docker system df, and pruning stopped containers, images, volumes, networks, build cache, or everything. Each shows the exact command and asks first.