Fix wrapping swarm states (#6438)

This commit is contained in:
Gwendolynne Barr 2018-04-12 08:12:56 -07:00 committed by GitHub
parent 88eedbf8b2
commit 3243cec451
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 4 deletions

View File

@ -6,8 +6,9 @@ redirect_from:
- /datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-task-state/
---
Docker lets you create services, which can start tasks. A service is a description of a desired state, and a task does the work.
Work is scheduled on swarm nodes in this sequence:
Docker lets you create services, which can start tasks. A service is a
description of a desired state, and a task does the work. Work is scheduled on
swarm nodes in this sequence:
1. Create a service by using `docker service create` or the UCP web UI or CLI.
2. The request goes to a Docker manager node.
@ -15,9 +16,13 @@ Work is scheduled on swarm nodes in this sequence:
4. Each service can start multiple tasks.
5. Each task has a life cycle, with states like `NEW`, `PENDING`, and `COMPLETE`.
Tasks are execution units that run once to completion. When a task stops, it isn't executed again, but a new task may take its place.
Tasks are execution units that run once to completion. When a task stops, it
isn't executed again, but a new task may take its place.
Tasks advance through a number of states until they complete or fail. Tasks are initialized in the `NEW` state. The task progresses forward through a number of states, and its state doesn't go backward. For example, a task never goes from `COMPLETE` to `RUNNING`.
Tasks advance through a number of states until they complete or fail. Tasks are
initialized in the `NEW` state. The task progresses forward through a number of
states, and its state doesn't go backward. For example, a task never goes from
`COMPLETE` to `RUNNING`.
Tasks go through the states in the following order: