Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Did anything change w/ cloud use case?

See original GitHub issue

I’m rerunning the same cloud-deploy workflow as last week, but for some reason getting an error I’ve never seen before.

Run echo "Deploying..."
Deploying...
Creating CA: /github/home/.docker/machine/certs/ca.pem
Creating client certificate: /github/home/.docker/machine/certs/cert.pem
Running pre-create checks...
Creating machine...
(cml1593467392) Launching instance...
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)...
Error creating machine: Error running provisioning: Failed to obtain lock: Maximum number of retries (60) exceeded
The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.

Were there any changes to the cloud-runner image in the last four days that might be causing this?

Issue Analytics

State:
Created 3 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

elleobriencommented, Jun 29, 2020

very interesting. I’ll definitely put a note in the README when we release that GPUs/AMIs are not always consistent. you’re right that’s a good reason to have a custom image

1reaction

DavidGOrtegacommented, Jun 29, 2020

AMI are not consistant, thats one of the reasons we have to build ours, also, gpus are not always available. Sometimes i have found 0 availability for gpu in a specific region