Issue creating droplets with DO

[Hyperbytes]

I have been having big issues with docker remote recently with droplet creation failing.
last time this happened i just kept doing it and eventually after about 10 tried it worked but it is a bit of a pain. The droplet seems to be created but does not respond

Using Digital Ocean

Anyone any ideas why it is happening?

OUTPUT

Running pre-create checks…
Creating machine…
(cyber) Creating SSH key…
(cyber) Creating Digital Ocean droplet…
(cyber) 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)…
Running pre-create checks…
Creating machine…
(cyber) Creating SSH key…
(cyber) Creating Digital Ocean droplet…
(cyber) 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

Error Creating Docker Machine!

[Hyperbytes]

I see this in Wappler

[Teodor]

Looking at the error message, seems something is wrong on Digital Ocean, with the latest docker version - check:

Unable to verify the Docker daemon is listening | DigitalOcean

Maybe @George has a better idea of what goes wrong exactly.

[borbinka2]

Hi,

I (still) have a similar issue, check this workaround maybe it will work for you as well.

Error creating docker machine

My bad, I have a problem when creating a new remote docker machine. (I destroyed the old one before ressetting to a previous commit, as I believed that creating a new one will solve the problem). The exact error message is: Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded

Full log

Running pre-create checks... (ArmadaTwo) Generating a secure disposable linode-root-pass... Creating machine... (ArmadaTwo) …

@George, any chance that this is related to Wappler after all? Still not working on any provider, even after clean install.

[sitestreet]

This is what makes me nervous transitioning to NodeJS from PHP.

[max_gb]

Docker isn’t required for Node, I switched from PHP and either run sites on a VPS or via cPanel if it’s a managed server

[Teodor]

@sitestreet nothing to do with the server model actually. This seems to be some issue with docker.

@Hyperbytes please try George’s suggestion from the linked topic.

[George]

Well just as with any big software distribution, also docker has seem to have broken their latest docker version.

Latest docker release (20.10.0) doesn't work with docker-machine

seems there is a way to choose the docker version used, so I will add a choice for the next update.

They will probably be fixing it soon as well.

Note this is just for brand new server provisioning. It is also general docker, so not really digital ocean related.

[Hyperbytes]

Don’t really understand what i am supposed to do never mind get it working!

[Teodor]

Hey Brian,
Was referring to:

[Hyperbytes]

I stopped the container and started again and it is now showing running.
I will try a test deploy one i finish setup and advise

[Hyperbytes]

That seems to have it working correctly, website deployed and running.

Huge thanks as always Teodor/George

[George]

In the next update, we will use a specific docker version, so build errors with the latest version will be avoided as well

[borbinka2]

Thank you George!

[Teodor]

This has been fixed in Wappler 3.7.5