From 2824f8b96bea4d85a8c20dc0686ae4e70ba80758 Mon Sep 17 00:00:00 2001 From: test2 Date: Thu, 2 Apr 2020 02:16:37 +0300 Subject: [PATCH] swarm --- DockerSwarm/Creaate-Swarm.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/DockerSwarm/Creaate-Swarm.adoc b/DockerSwarm/Creaate-Swarm.adoc index b0f2375..bc98c23 100644 --- a/DockerSwarm/Creaate-Swarm.adoc +++ b/DockerSwarm/Creaate-Swarm.adoc @@ -262,9 +262,9 @@ docker node inspect id | jq -r '.[]["Status"]["State"]' To deploy an application image when Docker Engine is in swarm mode, you *create a service.* -A service is the image for a microservice within the context of some larger application. +A *service* is the image for a microservice within the context of some larger application. -Examples of services might include an HTTP server, a database, or any other type of executable program that you wish to run in a distributed environment. +`_Examples of services might include an HTTP server, a database, or any other type of executable program that you wish to run in a distributed environment._` @@ -273,7 +273,7 @@ A *task* is the atomic unit of scheduling within a swarm. When you declare a desired service state by creating or updating a service, the orchestrator realizes the desired state by scheduling tasks. -For instance, you define a service that instructs the orchestrator to keep three instances of an HTTP listener running at all times. +`_For instance, you define a service that instructs the orchestrator to keep three instances of an HTTP listener running at all times. _` The orchestrator responds by creating three tasks. @@ -457,6 +457,7 @@ networks: ---- +.replicas-vs-global image:./replicated-vs-global.png[alt="replica-vs-global"] + @@ -490,7 +491,7 @@ docker stack deploy -c run.yml my_service ---- -==== Lists services +==== List services .List the services that are running as part of the specified stack. [source,sh]