toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update cURL example for cURL 7.40 differences

Browse Source 
cURL 7.50 changed the validation for URL's
when using socket connections. cURL 7.4x
did not expect a hostname, whereas cURL
7.5x and above _requires_ a hostname.

See https://github.com/curl/curl/issues/936

This updates the example to take both
versions into account, because cURL 7.4x
is still widely used by distros.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: 2e0d6e6be2294ef2561e8c3b5f750fd814536268
Component: engine
This commit is contained in:
Sebastiaan van Stijn
2016-10-21 11:40:58 -07:00
parent 3b96eed08f
commit 871253dbbe
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
components/engine/docs/reference/api/docker_remote_api.md
View File

@ -33,7 +33,17 @@ later, as these versions have the `--unix-socket` flag available. To
run `curl` against the daemon on the default socket, use the
following:
curl --unix-socket /var/run/docker.sock http://localhost/containers/json
When using cUrl 7.50 or later:
```console
$ curl --unix-socket /var/run/docker.sock http://localhost/containers/json
```
When using cURL 7.40, `localhost` must be omitted:
```console
$ curl --unix-socket /var/run/docker.sock http://containers/json
```
If you have bound the Docker daemon to a different socket path or TCP
port, you would reference that in your cURL rather than the