Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Problem (Unable to remove from the database. Exit code: 1) lauching docker Stable in a Windows 10 pro virtual machine (installed on the VirtualBox Hypervisor) #34

Closed
ftheodule opened this issue Aug 10, 2016 · 2 comments

Comments

@ftheodule
Copy link

  • Diagnostic ID from "Diagnose & Feedback" in the menu.
    B09AF01B-E38D-4EF5-8248-2BBFFC3539E4/2016-08-10_15-08-45
  • 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)

This problem is reproductible; logs tell :
Failed to set up server socket listening on "hyperv-connect://72807d72-f692-4a03-a430-c76fb90ba0cd": Unix.Unix_error(Unix.ENETDOWN, "socket", "")

Windows 10 Pro Version 1511(version du systeme d'exploitation 10586.494) 3.5 Gbyte RAM, 2 cpu, Vt-x/Amd-V Active, service HyperV running

Context:
This Windows 10 Pro is installed in a VirtualBox hypervisor (5.0.24 r108.355) which is running on a Windows 7 (version 6.1 number 7601 service pack 1)

Steps to reproduce the behavior

  1. ...Use a Windows 7 64 bits running in a physical machine
  2. ... Install Virtual Box in this physical win 7
    3.. Install a Windows 10 pro (which will be virtual) in this Virtual Box
    4 .. Install docker for Windows in this Windows 10 Pro Virtual machine

FX Theodule

@rn
Copy link
Contributor

rn commented Aug 11, 2016

Thank you for your report. Unfortunately we not support running Docker for Windows in a Windows 10 Pro VM. Docker for Windows relies on Hyper-V which in turn requires hardware virtualisation support. If you run Windows 10 In a VM, your Hypervisor (Virtual Box in your case) must support a feature called nested virtualisation, which is very hard to get working correctly. According to this issue VirtualBox does not seem to support Nested Virtualisation.

Closing this issue

@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 17, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

3 participants