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
[Mac] docker-compose won't run due to "Couldn't connect to Docker daemon" error #2180
Comments
We recently fixed this error message (the fix will be in the next release). It should say "you might need to run If you still can't connect, and the |
Ok thanks. Looks like my issue is with the Docker VM. It's giving me all sorts of TLS errors even when running regular docker commands like
I'll take it up with the docker team. UPDATE For anyone also having this issue. The solution for me was to:
Apparently you need to run the |
I getting the same error, but I don't want to use the default machine but rather another machine created with the |
Yes. Compose will use whatever engine is set in the |
ah thanks, I didn't know about |
I'd just like to add something for anyone who visits this in the future... I keep having this issue every time I open a new shell, so I added |
Yes it works. But why eval $(docker-machine env default) suddenly. It was working fine before |
Yeah, I'm not sure either. Was working for me earlier as well. |
|
Eval "$(docker-machine env default)" worked, thanks! |
I'm still not totally happy with the solution of adding |
@shankiesan |
Hah yes I guess that wouldwork @michahell . Still have to do something before every time you use docker. Not ideal, but not bad! |
@shankiesan The only other option I can see is to export the variables produced from |
That's a good idea @lewistaylor . I tried that before it didn't work, but it has this time so it must have been operator error. Nice one, that's a great suggestion 👍 |
@shankiesan @lewistaylor wow, can't understand I didn't come up with that. even better solution 👍 |
this issue still persist , the only solution is to use
|
Sometimes I have the same issue BUT it comes up ONLY when I close my macbook. If I restart the system it may start fine, may not. If not I restart again and it's usually working. My guess is that probably the problem in the IP/ports, only guess, cause if I restart my laptop with unclosed programs (like PHPStorm) it usually won't work. If I close all the running programs and restart it, it's working. |
+1 |
@lewistaylor @shankiesan @michahell How do you export the variables from |
Drop docker-machine/dinghy/boot2docker and use docker for mac, it's set to
|
@nwshane Just edit
That should do it. |
@shankiesan Great, thanks! That did the trick. I was confusing myself by thinking that I had to run |
Here is my information, everything works fine if I use Could help me find out what is wrong? |
i am having the same issue |
|
Had the same problem with one specific service in docker-compose. Was a permissions issue... the files to be uploaded to docker were not owned by the current user. |
Same as @Rots here =/ |
paste the command: |
|
SSL error: EOF occurred in violation of protocol (_ssl.c:777) |
I'm very confused about how docker-compose is supposed to work on my Mac. Here are the steps I took:
docker-compose up
but gotIllegal instruction: 4
error as per Illegal instruction: 4 #1885docker-compose
with pip viasudo pip install -U docker-compose
docker-compose up
I getCouldn't connect to Docker daemon - you might need to run
boot2docker up.
Which is very confusing because all the documentation says that
boot2docker
is deprecated. And trying to install boot2docker isn't working for me either.I'm not sure what else to try. Currently have docker-compose v1.4.2 installed.
The text was updated successfully, but these errors were encountered: