search

docker / machine

Machine management for a container-centric world
https://docs.docker.com/machine/
Apache License 2.0
6.63k stars 1.96k forks source link

Certificate signed by unknown authority #4049

Open brandontamm opened 7 years ago

brandontamm commented 7 years ago

➜ machine git:(master) ✗ docker-machine ssh fr6 GET https://api.digitalocean.com/v2/droplets/xxxxxxxxx: 503 Failed to forward the request you made, please try again. ➜ machine git:(master) ✗ cd machine cd: no such file or directory: machine ➜ machine git:(master) ✗ docker-machine ssh fr6 GET https://api.digitalocean.com/v2/droplets/xxxxxxxxx: 503 Failed to forward the request you made, please try again. ➜ machine git:(master) ✗ docker-machine ssh fr6 Get https://api.digitalocean.com/v2/droplets/xxxxxxxxx: x509: certificate signed by unknown authority ➜ machine git:(master) ✗ docker-machine ssh fr6 Get https://api.digitalocean.com/v2/droplets/xxxxxxxxx: x509: certificate signed by unknown authority ➜ machine git:(master) ✗ docker-machine ssh fr6 GET https://api.digitalocean.com/v2/droplets/xxxxxxxxx: 503 Failed to forward the request you made, please try again. ➜ machine git:(master) ✗

brandontamm commented 7 years ago

I just started receiving these errors and do not know the steps I should take to fix the issue.

I am using Docker For Mac:

mxlje commented 7 years ago

I have the same errors, but they are not always reproducible. Sometimes running docker-machine ls again either has no errors, or a different machine shows the error message Get https://api.digitalocean.com/v2/droplets/{ID}: x509: certificate signed by unknown authority.

Jestre commented 7 years ago

I just discovered docker-machine and thought I would give it a try, so I am following the docs for using it with DigitalOcean, but I, too, get the certificate error:

$ docker-machine create --driver digitalocean --digitalocean-access-token xxx kanban
Running pre-create checks...
Error with pre-create check: "Get https://api.digitalocean.com/v2/regions: x509: certificate signed by unknown authority"

$ docker -v
Docker version 17.03.1-ce, build c6d412e

$ docker-machine -v
docker-machine version 0.10.0, build 76ed2a6
brandontamm commented 7 years ago

I usually get the error on the first attempt and then the next attempt lets me in. Sometimes it's more than one time I get the error before I get in.

vitaly commented 7 years ago

same problem

ajoybhatia commented 7 years ago

I have the same problem, no matter how many times I run the command. My Docker versions are:

%> docker --version
Docker version 17.06.1-ce, build 874a737
%> docker-machine --version
docker-machine version 0.12.0, build 45c69ad

Here is my console output:

%> docker-machine create --driver virtualbox myvm1
Running pre-create checks...
(myvm1) Default Boot2Docker ISO is out-of-date, downloading the latest release...
(myvm1) Latest release for github.com/boot2docker/boot2docker is v17.07.0-ce
(myvm1) Downloading /Users/ajbhatia/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v17.07.0-ce/boot2docker.iso...
Error with pre-create check: "Get https://github-production-release-asset-2e65be.s3.amazonaws.com/14930729/67d8c388-8d66-11e7-837a-e99cf6afe3d6?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170901%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170901T201410Z&X-Amz-Expires=300&X-Amz-Signature=8f4e789bfc950b84574a34f50d42cfbc50e90c82e3bf970e7be6ca8d085fd82d&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dboot2docker.iso&response-content-type=application%2Foctet-stream: x509: certificate signed by unknown authority"
ajoybhatia commented 7 years ago

In my case, it looks like docker-machine trying to download the latest release of boot2docker.iso was causing the problem. I downloaded the .iso from github.com by navigating to the URL with my browser. After that, the 'docker-machine create .... ' command ran successfully.