-
Notifications
You must be signed in to change notification settings - Fork 54
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
Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening #54
Comments
I was running into exactly the same issue and can confirm that downgrading docker fixes the issue:
|
Hi, this seems to be a core docker-machine issue, as you have already confirmed by your edit. Could you verify @sokraflex's workaround and see if that fixes the issue for you please? Even if it does not, I don't think there is anything the driver can do here. I'll close this, as it is out-of-scope, but feel free to use this thread for further discussion. |
Ran into the exact same issue. Apparently it has something to do with the latest docker version 20.10 which was released yesterday. Downgrading docker via |
Same issue here. Workaround with downgrading docker works. |
Is this still an issue? |
Yes, I still get the same error with Docker version 20.10.4, build d3cb89e |
I was also suffering from this problem but I fixed it by restarting the Docker service after Docker Machine modifies its configuration. [[runners]]
[runners.machine]
MachineOptions = [
"""hetzner-user-data=
#cloud-config
runcmd:
- |
while sleep 1; do
if [ -e /etc/systemd/system/docker.service.d/10-machine.conf ]; then
systemctl restart docker
break
fi
done &
"""
] |
Had to modify the format of solution by @hectorm a bit, but with this it's working great now:
|
@hectorm 's workaround almost worked for me. Had to add a small delay:
|
Hi all
I have been using this library for a couple of weeks now and did not face any issues.
Since this morning, I run into the following error:
Here the full log:
Anyone has any clues what I could try?
Edit: Found this related issue: docker/machine#4858 (comment).
The text was updated successfully, but these errors were encountered: