-
Notifications
You must be signed in to change notification settings - Fork 7
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
docker-machine Cannot connect to the docker engine endpoint (centos-7) #4
Comments
@tianon will be better able to speak to this than me, but I think the cert generation is handled in Docker Machine separately from what this driver does. I believe the driver is just responsible for provisioning the machine and then it hands the ssh details off to Docker Machine for installation of Docker. My suspicion is the problem could be in the CentOS image or it could be in Docker Machine itself and how it attempts to configure on top of CentOS. That doesn't do anything to fix the problem, but it's what I know of it so far. In terms of what to do next, the next question I have is if CentOS machines work with other cloud drivers? |
@misterbisson is correct -- |
Does it work with earlier versions of the CentOS image, like centos-7@20161028 ? |
I tested 20161028 and 20160415 images, both gave the same error. |
Disabling firewalld lets the connection through. firewalld and docker issue documented here
|
em... i got a similar problem.rm machine and recreate also occure, let me surprice that the problem occure when i creat bridged.can tel me how deal, if you done |
recreate, can work |
have you resolved this issue in a polite way instead arbitrarily recreate a VM? |
I have something similar... it's because the default docker installed on the remove system is not running the different listeners and quite possibly also missing the certificates. (I have the same issue trying to |
docker-machine
works fine with debian, but when creating a centos machine, it throws an error about not being able to connect to docker engine endpoint.The text was updated successfully, but these errors were encountered: