docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

added comprehensive list of swarm states (#2552) 

Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
This commit is contained in:
Victoria Bialas 2017-03-30 00:09:24 -04:00 committed by GitHub
parent bc4eb8d5f0
commit bfca2777ae
1 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docker-cloud/cloud-swarm/register-swarms.md
View File

@ -76,13 +76,25 @@ You can now access this cluster using the following command in any Docker Engine
Swarms that are registered in Docker Cloud appear in the Swarms list. Each line in the list shows the swarm's status. The statuses are:
<!-- TODO - **DEPLOYING**: Docker Cloud is provisioning the nodes of this swarm. -->
- **DEPLOYED**: the swarm is sending heartbeat pings to Docker Cloud, and Cloud can contact it to run a health check.
- **UNREACHABLE**: the swarm is sending heartbeat pings, but Docker Cloud cannot contact the swarm.
- **UNAVAILABLE**: Docker Cloud is not receiving any heartbeats from the swarm.
- **REMOVED**: the swarm has been unregistered from Docker Cloud and will be removed from the list soon.
| Status | Description | Actions |
|:---------------|:--------------------------------------------------------|:---------------------------------|
| **DEPLOYING** | Docker Cloud is in the process of provisioning the swarm. | None |
| **DEPLOYED** | The swarm is running, connected, and sending heartbeat pings to Docker Cloud, and Cloud can contact it to run a health check. | All (Edit endpoint, view logs, review, terminate) |
| **UNREACHABLE** | The swarm is sending heartbeat pings and Docker Cloud is receiving them, but Cloud cannot connect to the swarm. | Remove |
| **UNAVAILABLE** | Docker Cloud is not receiving heartbeats from the swarm. | Remove |
| **TERMINATING** | Docker Cloud is in the process of destroying this swarm. | None |
| **TERMINATED** | The swarm has been destroyed and be removed from the list in 5 minutes. | None |
| **REMOVED** | The swarm was unregistered from Docker Cloud but not destroyed. The swarm will be removed from list in 5 minutes. | None |
| **FAILED** | Provisioning failed. Please view logs for details. | View logs, remove |
> **Note**: [Removing a swarm](#unregister-a-swarm-from-docker-cloud) only removes the swarm from the interface in Docker Cloud. It does not change the swarm itself or any processes running on the swarm.
### Understanding and resolving problems
* If a swarm is publicly UNREACHABLE, it may be behind a firewall or NAT.
* If a swarm is UNAVAILABLE check the swarm from your infrastructure provider. The manager node(s) may be unresponsive or the server proxy service might not be running. You can SSH into an UNAVAILABLE swarm.
* Removing a swarm only removes the swarm from the interface in Docker Cloud (i.e., [unregisters](#unregister-a-swarm-from-docker-cloud) it). It does not
change the swarm itself or any processes running on the swarm.
## Unregister a swarm from Docker Cloud