Environments

An environment is one Docker server with its agent. The Environments page lists them all with their status, Docker and agent version, containers, CPU and memory. To add one, see Add more servers.

An environment is Online while its agent is connected. When it is Offline, you still see its last known state, but actions on it are off until it reconnects. Its page says when its agent was last seen and which address it connects to. On the pages of its stacks, containers, images, volumes and networks, the same notice links here.

If it stays Offline:

1. Check that the agent runs on that server. What to Check opens Troubleshooting.
2. If the agent can't connect any more, for example because its volume was lost, press New Install Command and run the command on that server. The new agent replaces the old one. An agent shown as Too Old or Too New needs an upgrade instead, so the page doesn't offer one.

An environment's pageCopy Anchor Link

• Overview: CPU, memory, disk, uptime, the number of containers, images, volumes and networks, and the server's and its containers' charts (see Metrics).
• System: details about the server and Docker on it, and the health of its disks and RAID arrays (see Monitoring).
• Agents: the agent, its version and when it was last seen.
• Jobs: the latest jobs on this server.

While the environment has no stacks, the Overview offers to import the Compose projects found on the server (Import 2 Projects, for example) and Create Stack. More Actions has Import Projects and Create Stack too.

Edit changes the Name and the Service Address: the host name or IP address you open this server's apps at. With it set, published ports become links.

Archive an environmentCopy Anchor Link

To stop managing a server, choose More Actions → Archive Environment. Docker Manager first shows what depends on it. Archiving:

• disconnects the agent for good and ends its jobs in Docker Manager. A job the agent was running goes on there on its own; if it still runs when you re-attach the environment, Docker Manager stops it and records what it did,
• keeps the stacks, settings, history and backups, so you can bring it back; its backups keep following retention, and a Recovery Key rotation moves them too,
• removes the permissions given for this environment,
• changes nothing on the server. Remove the agent container there yourself if you no longer need it.

To keep its stacks under Docker Manager, migrate them to another server first. Archived environments are on the Archived tab.

Re-attach an environmentCopy Anchor Link

Re-Attach reconnects a server Docker Manager already knows: after you archived it, removed its agent or recovered Docker Manager from a backup.

1. Open the environment and press Re-Attach (also on its Agents tab).
2. Press Create Install Command and run the command on that server. On Docker Manager's own server, use the On the Docker Manager Server tab.

Manage the agentCopy Anchor Link

On the Agents tab, the agent's menu has:

• Remove Agent: the agent can no longer connect. Type the environment's name to confirm. Nothing on the server changes.
• Rotate Credential: gives the agent a new secret, if you think the old one leaked.

An agent one release behind Docker Manager shows Outdated and still works, except that it can't restore backups: upgrade it to Docker Manager's version first. An older agent (Too Old) is refused until you upgrade it; one newer than Docker Manager (Too New) is refused until you upgrade Docker Manager.