These Markdown files are now embedded in a YAML file for templating in the documentation, and these special markers are no longer needed. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
		
			
				
	
	
	
	
		
			4 KiB
		
	
	
	
	
	
	
	
			
		
		
	
	| title | description | keywords | 
|---|---|---|
| service inspect | The service inspect command description and usage | service, inspect | 
service inspect
Usage:  docker service inspect [OPTIONS] SERVICE [SERVICE...]
Display detailed information on one or more services
Options:
  -f, --format string   Format the output using the given Go template
      --help            Print usage
      --pretty          Print the information in a human friendly format
Description
Inspects the specified service. This command has to be run targeting a manager node.
By default, this renders all results in a JSON array. If a format is specified, the given template will be executed for each result.
Go's text/template package describes all the details of the format.
Examples
Inspect a service by name or ID
You can inspect a service, either by its name, or ID
For example, given the following service;
$ docker service ls
ID            NAME   MODE        REPLICAS  IMAGE
dmu1ept4cxcf  redis  replicated  3/3       redis:3.0.6
Both docker service inspect redis, and docker service inspect dmu1ept4cxcf
produce the same result:
$ docker service inspect redis
[
    {
        "ID": "dmu1ept4cxcfe8k8lhtux3ro3",
        "Version": {
            "Index": 12
        },
        "CreatedAt": "2016-06-17T18:44:02.558012087Z",
        "UpdatedAt": "2016-06-17T18:44:02.558012087Z",
        "Spec": {
            "Name": "redis",
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "redis:3.0.6"
                },
                "Resources": {
                    "Limits": {},
                    "Reservations": {}
                },
                "RestartPolicy": {
                    "Condition": "any",
                    "MaxAttempts": 0
                },
                "Placement": {}
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "UpdateConfig": {},
            "EndpointSpec": {
                "Mode": "vip"
            }
        },
        "Endpoint": {
            "Spec": {}
        }
    }
]
$ docker service inspect dmu1ept4cxcf
[
    {
        "ID": "dmu1ept4cxcfe8k8lhtux3ro3",
        "Version": {
            "Index": 12
        },
        ...
    }
]
Formatting
You can print the inspect output in a human-readable format instead of the default
JSON output, by using the --pretty option:
$ docker service inspect --pretty frontend
ID:		c8wgl7q4ndfd52ni6qftkvnnp
Name:		frontend
Labels:
 - org.example.projectname=demo-app
Service Mode:	REPLICATED
 Replicas:		5
Placement:
UpdateConfig:
 Parallelism:	0
 On failure:	pause
 Max failure ratio:	0
ContainerSpec:
 Image:		nginx:alpine
Resources:
Networks:	net1
Endpoint Mode:  vip
Ports:
 PublishedPort = 4443
  Protocol = tcp
  TargetPort = 443
  PublishMode = ingress
You can also use --format pretty for the same effect.
Find the number of tasks running as part of a service
The --format option can be used to obtain specific information about a
service. For example, the following command outputs the number of replicas
of the "redis" service.
$ docker service inspect --format='{{.Spec.Mode.Replicated.Replicas}}' redis
10