Question
Unable to verify the Docker daemon is listening
- Posted on December 21, 2020
- DockerDigitalOcean
Asked by jefftully
As I was following a tutorial on how to use docker-machine create I got stuck with docker-machine create --digitalocean-size “s-2vcpu-4gb” --driver digitalocean --digitalocean-access-token “token here” “server name”
Creating machine… (keycloakexperiment1) Creating SSH key… (keycloakexperiment1) Creating Digital Ocean droplet… (keycloakexperiment1) Waiting for IP address to be assigned to the Droplet… Waiting for machine to be running, this may take a few minutes… Detecting operating system of created instance… Waiting for SSH to be available… Detecting the provisioner… Provisioning with ubuntu(systemd)… Installing Docker… Copying certs to the local machine directory… Copying certs to the remote machine… Setting Docker configuration on the remote daemon… Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded It changes, nothing googled makes sense because any fix has to me enacted on creation.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Workaround:
docker-machine create \
--driver digitalocean \
--digitalocean-access-token $DOTOKEN \
--engine-install-url "https://releases.rancher.com/install-docker/19.03.9.sh" \
name;
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
What I am doing wrong here? I am using Windows 10.
This comment has been deleted
Turns out, the issue is with the new Docker version. You can try the older version by supplying a URL from which the Docker Engine can be downloaded like this: