Clarify the DRAIN state w/ regard to containers (#5811)

* Clarify the DRAIN state w/ regard to containers

Bare containers are not state-reconciled, and are not affected by the swarm DRAIN state
This commit is contained in:
ada 2018-01-24 14:35:53 -05:00 committed by Misty Stanley-Jones
parent b68eee92b0
commit dd7a802a9d
1 changed files with 6 additions and 0 deletions

View File

@ -14,6 +14,12 @@ availability. `DRAIN` availability prevents a node from receiving new tasks
from the swarm manager. It also means the manager stops tasks running on the from the swarm manager. It also means the manager stops tasks running on the
node and launches replica tasks on a node with `ACTIVE` availability. node and launches replica tasks on a node with `ACTIVE` availability.
> **Important**: Setting a node to `DRAIN` does not remove standalone containers from that node,
> such as those created with `docker run`, `docker-compose up`, or the Docker Engine
> API. A node's status, including `DRAIN`, only affects the node's ability to schedule
> swarm service workloads.
{:.important}
1. If you haven't already, open a terminal and ssh into the machine where you 1. If you haven't already, open a terminal and ssh into the machine where you
run your manager node. For example, the tutorial uses a machine named run your manager node. For example, the tutorial uses a machine named
`manager1`. `manager1`.