Browse code
Document alternate command to check encrypted TCP socket as curl command seems to fail on OSX Mavericks
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Nicolas De loof authored on 2014/10/18 19:58:20Showing 1 changed files
| ... | ... |
@@ -8,8 +8,10 @@ page_keywords: API, Docker, rcli, REST, documentation |
| 8 | 8 |
and the client must have `root` access to interact with the daemon. |
| 9 | 9 |
- If the Docker daemon is set to use an encrypted TCP socket (`--tls`, |
| 10 | 10 |
or `--tlsverify`) as with Boot2Docker 1.3.0, then you need to add extra |
| 11 |
- parameters to `curl` when making test API requests: |
|
| 11 |
+ parameters to `curl` or `wget` when making test API requests: |
|
| 12 | 12 |
`curl --insecure --cert ~/.docker/cert.pem --key ~/.docker/key.pem https://boot2docker:2376/images/json` |
| 13 |
+ or |
|
| 14 |
+ `wget --no-check-certificate --certificate=$DOCKER_CERT_PATH/cert.pem --private-key=$DOCKER_CERT_PATH/key.pem https://boot2docker:2376/images/json -O - -q` |
|
| 13 | 15 |
- If a group named `docker` exists on your system, docker will apply |
| 14 | 16 |
ownership of the socket to the group. |
| 15 | 17 |
- The API tends to be REST, but for some complex commands, like attach |