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

Merge pull request #541 from thaJeztah/fix-service-create-markdown 

Fix service_create markdown
This commit is contained in:
Sebastiaan van Stijn 2017-09-19 17:17:45 +02:00 committed by GitHub
parent b3aa1195d4 01ef9acd31
commit 68935944b3
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/reference/commandline/service_create.md
View File

@ -159,7 +159,7 @@ $ docker service create --name redis --secret secret.json redis:3.0.6
4cdgfyky7ozwh3htjfw0d12qv 4cdgfyky7ozwh3htjfw0d12qv
``` ```
Create a service specifying the secret, target, user/group ID and mode: Create a service specifying the secret, target, user/group ID, and mode:
```bash ```bash
$ docker service create --name redis \ $ docker service create --name redis \
@ -398,7 +398,7 @@ For more information about bind propagation, see the
#### Options for Named Volumes #### Options for Named Volumes
The following options can only be used for named volumes (`type=volume`); The following options can only be used for named volumes (`type=volume`):
<table> <table>
@ -419,7 +419,7 @@ The following options can only be used for named volumes (`type=volume`);
<td> <td>
One or more custom metadata ("labels") to apply to the volume upon One or more custom metadata ("labels") to apply to the volume upon
creation. For example, creation. For example,
`volume-label=mylabel=hello-world,my-other-label=hello-mars`. For more <tt>volume-label=mylabel=hello-world,my-other-label=hello-mars</tt>. For more
information about labels, refer to information about labels, refer to
<a href="https://docs.docker.com/engine/userguide/labels-custom-metadata/">apply custom metadata</a>. <a href="https://docs.docker.com/engine/userguide/labels-custom-metadata/">apply custom metadata</a>.
</td> </td>
@ -430,8 +430,8 @@ The following options can only be used for named volumes (`type=volume`);
By default, if you attach an empty volume to a container, and files or By default, if you attach an empty volume to a container, and files or
directories already existed at the mount-path in the container (<tt>dst</tt>), directories already existed at the mount-path in the container (<tt>dst</tt>),
the Engine copies those files and directories into the volume, allowing the Engine copies those files and directories into the volume, allowing
the host to access them. Set `volume-nocopy` to disables copying files the host to access them. Set <tt>volume-nocopy</tt> to disable copying files
from the container's filesystem to the volume and mount the empty volume. from the container's filesystem to the volume and mount the empty volume.<br />
A value is optional: A value is optional: