From 2e0d6e6be2294ef2561e8c3b5f750fd814536268 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Fri, 21 Oct 2016 11:40:58 -0700 Subject: [PATCH] Update cURL example for cURL 7.40 differences 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 --- docs/reference/api/docker_remote_api.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/reference/api/docker_remote_api.md b/docs/reference/api/docker_remote_api.md index b95112f0c4..211931cc2e 100644 --- a/docs/reference/api/docker_remote_api.md +++ b/docs/reference/api/docker_remote_api.md @@ -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