Containers

Containers lists every container on your servers with its status, stack, CPU, memory, uptime, networks and ports. Search by name, image, address or label, and filter by status, stack or available updates.

Start, stop and removeCopy Anchor Link

On a container's page, the main button is Stop while the container runs and Start when it doesn't; its menu adds Restart. Next to it, Pause freezes a running container and Unpause resumes it. Remove is under More Actions. Each row's menu in the list has the same actions. Stop asks first; Remove asks you to type the container's name.

To act on several containers, select their rows and pick an action in the bar above the list. On a phone the bar sits at the bottom of the screen; with more than two actions, all but the first are under More Actions. Start and Restart run at once; Stop and Remove first show what they run on. Containers an action can't run on are left out, with the reason. Each row's Status shows the progress; if anything fails, the closing message stays until you close it and offers View Failed Jobs.

You can start and stop the containers of a Docker Manager stack here, but you change or remove them through the stack.

Recreate a containerCopy Anchor Link

Recreate replaces a container with a new one from the same settings.

1. On the container's page, open More Actions → Recreate (or the row's menu in the list).
2. Check what happens and press Recreate Container.

Good to know:

• Only for containers outside a stack or Compose project. For a stack's container, use Force Recreate in its service's row menu on the stack page.
• It uses the image as it is on the server now and downloads nothing. To run a newer version, pull the image on Images first.
• Volumes are kept. Changes made inside the container outside a volume are lost.
• The new container starts only if the old one was running.

A container's pageCopy Anchor Link

• Overview: CPU, memory, restarts and health, a chart, and its image, ports, networks, mounts, labels and limits. For containers Docker Manager created, it shows the names of the environment variables, never their values.
• Logs and Terminal: see Logs and Terminal.

Below its name, the page shows the container's image and stack. Both link to their pages (the stack when Docker Manager manages it).

Settings changes the restart policy and the CPU, memory and process limits. Other settings need a new container. Memory Limit (MB) is in decimal megabytes (1 MB = 1,000,000 bytes): Compose's 512m is 536.87 MB. A limit you don't change keeps its exact value.

Create a containerCopy Anchor Link

For a single container without a Compose file, press Create Container. Fill in the image (for example nginx:1.27) and a name, and optionally environment variables, ports, volumes, networks, restart policy, limits and, under Advanced, the command, user, health check and labels. Then press Create Container.

Creating never downloads the image: if it is missing, press Pull Image first. Environment variable values are stored encrypted and never shown again.

Docker Manager's own containersCopy Anchor Link

Docker Manager never stops, pauses, recreates or removes its own containers (Docker Manager and the Docker Agent), and never removes its own images, volumes or networks. Nobody can change this, not even the owner. Restarting one of them asks you to confirm first.