clearlinux/docker
2
0
Fork 0
mirror of https://github.com/clearlinux/docker.git synced 2026-10-03 23:38:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

unify –(en dash) to - when specifying options

Browse Source 
Signed-off-by: Xie Shi <georgexsh@gmail.com>
This commit is contained in:
George Xie
2014-11-05 13:50:59 +08:00
committed by Xie Shi
parent 0d513b5a84
commit c81337d5db
5 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/reference/api/docker_remote_api_v1.2.md
+1 -1
View File
@@ -979,4 +979,4 @@ To enable cross origin requests to the remote api add the flag
"--api-enable-cors" when running docker in daemon mode.
> docker -d -H="[tcp://192.168.1.9:2375](tcp://192.168.1.9:2375)"
> –api-enable-cors
> -api-enable-cors
docs/sources/reference/api/docker_remote_api_v1.3.md
+1 -1
View File
@@ -1064,4 +1064,4 @@ stdout and stderr on the same socket. This might change in the future.
To enable cross origin requests to the remote api add the flag
"--api-enable-cors" when running docker in daemon mode.
> docker -d -H="192.168.1.9:2375" –api-enable-cors
> docker -d -H="192.168.1.9:2375" -api-enable-cors
docs/sources/reference/api/hub_registry_spec.md
+1 -1
View File
@@ -458,7 +458,7 @@ on a private network without having to rely on an external entity
controlled by Docker Inc.
In this case, the registry will be launched in a special mode
(–standalone? ne? –no-index?). In this mode, the only thing which changes is
(-standalone? ne? -no-index?). In this mode, the only thing which changes is
that Registry will never contact the Docker Hub to verify a token. It will be
the Registry owner responsibility to authenticate the user who pushes
(or even pulls) an image using any mechanism (HTTP auth, IP based,