An error occurred trying to connect: Get https://192.168.xx.xx:2376/v1.18/containers/json: remote error: bad certificate #673
Comments
The following certs were automatically added to the following directory when i created the docker-machine
I tried changing the location of the cert with
But it just output the docker help list. |
I got the same error. $ docker ps
FATA[0001] An error occurred trying to connect: Get https://192.168.59.103:2376/v1.17/containers/json: Forbidden
$ docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): darwin/amd64
FATA[0001] An error occurred trying to connect: Get https://192.168.59.103:2376/v1.17/version: Forbidden Anybody can help? Thank you! |
The same error (client windows/amd64):
|
Try to remove the certificates in ~/.docker/machine/certs/ This worked for me. It seems you have older certs associated with the boot2docker image. |
Thank you, everybody. I just restart the boot2docker-vm machine. |
It did not work for me:
Ubuntu 14.10 |
I can confirm this error. I'm running of a new
Restart docker with
hasn't helped, neither has deleting the certs with
which now gives me the following error when I run
which makes sense. New to docker so completly lost on what could have caused the initial connection issue. I have already setup my dev environment with virtualbox so I'm wondering if the net config here could be a cause? |
... interestingly after doing the above (
|
Had a similar error as @gusun1 after upgrading boot2docker and running the following commands:
Worked fine, so I ran the hello-world:
Got a fatal, printed out the version and such
Then restarted:
Seemed to get the appropriate output after the restart. |
I am having the same problem as daithi-coombes However when I use the actual boot2docker vm I am able to run the command with no problem. |
Ok there are a few different issues here. @IbnSaeed if you use Machine 0.2.0 or higher the cert issue will be fixed when you run There are a few reports in this thread mixing the b2d cli and machine. While they both use the B2D ISO for the OS, they are separate tools and do not work with each others configurations. If you want to import an existing b2d VM that feature is in master and will be released in the upcoming 0.3.0. If you still have issues not related to certs, please open a new issue. Thanks! |
|
In case other people have the same issues as I did on Windows 64bit: https://x86x64.wordpress.com/2015/05/03/docker-on-windows-fata0021-an-error-occurred-trying-to-connect/ |
thanks @adamveld12, it worked for me. (win 8.1 64bit) |
The following commands worked for me. In command prompt:
After executing commands above, I closed my docker console and re-opened a new one. Tested it by running docker command FYI command removes images. UPDATE: |
@sbanal I think you meant you ran:
That worked for me. |
I just ran into this yesterday. Ran @eddietejeda fix above and that worked. I stopped everything. Today, I go and start everything back up. Same problem again. Seems kind of bad to have to constantly rebuild b2d every time I want to use it. I have b2d 1.7.0 installed via brew on OSX 10.10.4. |
boot2docker poweroff
boot2docker destroy
boot2docker init
boot2docker start This also worked for me! Just notice that I have to open new terminal window (to reset the DOCKER_ environment variables if you have set them before). Thanks! |
@sbanal It's work for me to on OSX too.
Thanks , saving ton of hours.! |
@sbanal thx! It's work for me. |
boot2docker poweroff |
I have this issue, but slightly different. This message keeps popping up when boot2docker isn't running. I don't really want it running all the time and the message goes when it is running. Has something been set to auto run each time I open a Terminal window? I can confirm, Docker is trying to run every time I launch a terminal window. Hmm… |
Seeing this with |
I'm on windows 8.1 boot2docker.exe download Worked for me. |
I'm fighting on Win8.1 with Docker Toolbox 1.8.1b and today 1.8.2a. Here the situation:
|
I have reported similar issue here. Docker is exhausting :( |
If you have installed docker toolbox then run docker quickstart terminal (it's a program and get installed during installation process). After this open a new command prompt window and run a docker command docker version. Works for me. |
For Docker Toolbox - |
Hello
I am getting the following error message when running . in windows 8.1
Here is the docker version command
Here is the docker-machine version
The text was updated successfully, but these errors were encountered: