-
Notifications
You must be signed in to change notification settings - Fork 109
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
Can't start docker daemon. #268
Comments
Looks like docker-machine is failing to bring up the VM. If you run In my experience, a lot of issues with Virtualbox tend to disappear after a reboot, sad as that is. |
Hi, Thanks for the reply and tips. :) I tried docker-machine start dinghy, the output I got was:
What is weird is the workaround.
It is as if dinghy waits for the Enter command. Regards. |
Did you upgrade to boot2docker 18.02 recently as well? We're seeing increased problems with it and had to rollback to 17.12 till 18.03 is released (as per #270): dinghy create --provider=virtualbox --boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v17.12.1-ce/boot2docker.iso |
Thanks @chinthakagodawita. I'll revert until 18.03 is released. Regards. |
i ran into similar problem. In my case, it's "incorrectly" configured Is there any way to get more info/logs from booting and process starting? Or start daemon process manually to get some output?
|
I'm looking at You can create and start the VM directly with If you're seeing an issue where you have to press Enter in the VM terminal before |
My case is a little bit different - i'm trying to disable "debug" flag for docker daemon, because Anyway, thanks to your comment i found what i was looking for in :) |
How would you revert an existing docker-machine @chinthakagodawita? |
Unfortunately, I don't know a way apart from re-creating it: dinghy destroy
dinghy create --provider=virtualbox --boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v17.12.1-ce/boot2docker.iso |
Good news, the dinghy upgrade command worked. It automatically downgraded to v17.12.1-ce. Wouldn't want to lose all my existing docker images. But alas the problem still persists! :( Still using the workaround. Thanks though for the response. JJ |
It sounds like this has been fixed upstream now with the 18.03 release, closing this issue. |
Hi,
Good day.
Upgraded to Virtualbox 5.2.6 r120293 on a Mac. The dinghy up command gives the following error:
Tried upgrading dinghy with upgrade command. It upgraded to:
That didn't help. Does dinghy require the Virtualbox tools installed or something?
Also, dinghy status gives:
Regards.
JJ
The text was updated successfully, but these errors were encountered: