Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certificate missing. #91

Closed
rominirani opened this issue Aug 14, 2015 · 15 comments

Comments

@rominirani
Copy link

@rominirani rominirani commented Aug 14, 2015

The default machine was created by QuickStart Terminal. When I try to do the following:

docker-machine env --shell cmd default

I get the following error:
open <filepath\ca.pem : The system cannot find the file specified.

I created another machine dev and this one goes through fine. So I am not sure what happened to the default one.

Environment : Windows

@gowthamgts

This comment has been minimized.

Copy link

@gowthamgts gowthamgts commented Aug 24, 2015

I'm also getting the same error.

@gimerstedt

This comment has been minimized.

Copy link

@gimerstedt gimerstedt commented Aug 25, 2015

experiencing the same issue on w7 using both the terminal as well as kitematic.

@bill2004158

This comment has been minimized.

Copy link

@bill2004158 bill2004158 commented Aug 26, 2015

I'm also getting the same error.

@LongLiveCHIEF

This comment has been minimized.

Copy link

@LongLiveCHIEF LongLiveCHIEF commented Aug 26, 2015

+1, running OSx 10.10.4

@mchiang0610 mchiang0610 changed the title Docker Machine Issue : env for default machine gives ca.pem file missing Certificate missing. Sep 9, 2015
@mchiang0610

This comment has been minimized.

Copy link
Contributor

@mchiang0610 mchiang0610 commented Sep 9, 2015

Just wanted to update that we are aware of this.

You can currently use docker machine to regenerate certs:

 docker-machine regenerate-certs default
@gowthamgts

This comment has been minimized.

Copy link

@gowthamgts gowthamgts commented Sep 9, 2015

The problem is solved for me by upgrading the Virtualbox to the test build version 5.0.3. Please try this.

@mchiang0610

This comment has been minimized.

Copy link
Contributor

@mchiang0610 mchiang0610 commented Sep 9, 2015

@gowthamgts Thanks. The issue can be sometimes solved by just running it again (which installing test build would do). We still have some users with the same problem with 5.0.3.

In any case, 5.0.4 is out, and we are testing with that.

@gowthamgts

This comment has been minimized.

Copy link

@gowthamgts gowthamgts commented Sep 9, 2015

Oh. May be in my case it worked well. 😄

@rominirani

This comment has been minimized.

Copy link
Author

@rominirani rominirani commented Sep 12, 2015

I upgraded to 1.8.1c , my VirtualBox is still 5.0.2 and the problem has gone away.

@defaria

This comment has been minimized.

Copy link

@defaria defaria commented Sep 15, 2015

running this worked for me. Thanks.
docker-machine regenerate-certs default

@T1m1

This comment has been minimized.

Copy link

@T1m1 T1m1 commented Sep 16, 2015

thanks @rominirani.
Worked for me, too.

@gerrywastaken

This comment has been minimized.

Copy link

@gerrywastaken gerrywastaken commented Sep 17, 2015

Just downloaded the latest docker toolbox and this bug still happens.

@tanepiper

This comment has been minimized.

Copy link

@tanepiper tanepiper commented Oct 20, 2015

I have the latest DockerToolbox (DockerToolbox-1.8.3) and VirtualBox 5.0.6 and I'm getting this on a clean install.

When I do docker-machine regenerate-certs default it just seems to hang there, this is using the Docker Quickstart Console.

Running on Windows 10

Edit: I've also tried to create a new docker image using docker-machine create tane-default --driver virtualbox - it seems to hang on Starting VM, but I can see in VirtualBox's preview window that the docker image is running and at a prompt. When I go in to view it I can see the likes of the server.pem file being created via the command line, but those files never appear in my Windows directory. I wonder if the issue could be related?

@mchiang0610

This comment has been minimized.

Copy link
Contributor

@mchiang0610 mchiang0610 commented Oct 21, 2015

Merging this with #153

@prayagupd

This comment has been minimized.

Copy link

@prayagupd prayagupd commented Dec 14, 2015

docker-machine regenerate-certs default

did the trick. (Thx to closed issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.