Skip to content
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

MobyLinuxVM failed to realize - fix #788

Closed
jeffstokes72 opened this issue Jun 2, 2017 · 7 comments
Closed

MobyLinuxVM failed to realize - fix #788

jeffstokes72 opened this issue Jun 2, 2017 · 7 comments

Comments

@jeffstokes72
Copy link

jeffstokes72 commented Jun 2, 2017

Expected behavior

Install Docker and have it start without error

Actual behavior

MobyLinuxVM failed to realize

Information

  • Diagnostic ID from "Diagnose & Feedback" in the menu.
    A556701F-1849-4397-BBE6-C4288D5C28AA/2017-06-02_03-30-47
  • a reproducible case if this is a bug, Dockerfiles FTW
  • page URL if this is a docs issue or the name of a man page
  • host distribution and version (Windows version, build number, etc)
    Win 10.0.16199.1000

Steps to reproduce the behavior

  1. install Docker (stable or edge)
  2. fail to launch Docker

I fixed this issue. It is documented here.
https://illuminati.services/2017/06/02/docker-on-windows-mobylinuxvm-failed-to-realize-fixed/

TL;DR hyper-v kept stale info with invalid paths to the VM storage area (registry, binary blob somewhere, who knows), Docker install picked them up and didn't pre-flight check them (presumably)

@jasonbivins
Copy link

Hi @jeffstokes72 thanks for posting!

@jasonbivins
Copy link

Hi @jeffstokes72

I captured this as a KB - I'll go ahead and close it now. Thanks again!

@judge2020
Copy link

Would like to note that it would be nice to provide a more descriptive message when this occurs, possibly run a pre-check to see if the Hyper-V folder exists on the system and warn if it isn't.

@DanTup
Copy link

DanTup commented May 17, 2019

This issue has a label of "status/3-fixed", but I just hit exactly the same issue today. I'd also deleted the Hyper-V folder after using it in the past, and Docker crashed with the same error.

@wrstlrlp13
Copy link

Can't believe Hyper-V doesn't realize those are wrong... Thanks!!!

@jeffstokes72
Copy link
Author

This issue has a label of "status/3-fixed", but I just hit exactly the same issue today. I'd also deleted the Hyper-V folder after using it in the past, and Docker crashed with the same error.

did you get the directory hyper-v thinks it's using for the store? It can be changed in the hyper-v server config. Sorry for my late reply.

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants