Closed ukienet closed 6 years ago
I'm seeing a different error:
C:\Source>docker run -it microsoft/nanoserver cmd docker: Error response from daemon: container e31cc45f5d4849055ff13566014c696cad5a5effc9702622c3524b43b3f9ea01 encountered an error during CreateContainer: failure in a Windows system call: No hypervisor is present on this system. (0xc0351000) extra info: {"SystemType":"Container","Name":"e31cc45f5d4849055ff13566014c696cad5a5effc9702622c3524b43b3f9ea01","Owner":"docker","IsDummy":false,"IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\ProgramData\Docker\windowsfilter\e31cc45f5d4849055ff13566014c696cad5a5effc9702622c3524b43b3f9ea01","Layers":[{"ID":"b43f5bf9-40d3-5fed-881c-105d1b4496cd","Path":"C:\ProgramData\Docker\windowsfilter\6214d91103e6aaf1ae8fca1a7312fa6939d1c0de4e13c19ead8915ccdf25745b"},{"ID":"eca436c3-1750-5858-ba86-380cd21bf844","Path":"C:\ProgramData\Docker\windowsfilter\8992d70442bb7e2c539993fd319fb91bfe0f20ed6a063fad9ab90a83882ebaff"}],"HostName":"e31cc45f5d48","MappedDirectories":[],"SandboxPath":"C:\ProgramData\Docker\windowsfilter","HvPartition":true,"EndpointList":["e18c867d-844c-47e1-aa0c-fc7f045062ea"],"HvRuntime":{"ImagePath":"C:\ProgramData\Docker\windowsfilter\6214d91103e6aaf1ae8fca1a7312fa6939d1c0de4e13c19ead8915ccdf25745b\UtilityVM"},"Servicing":false,"AllowUnqualifiedDNSQuery":true}.
@alexsab1 are you running on bare metal or in some sort of VM?
@Grauenwolf it looks like Hyper-V is not working on your system - can you create normal Hyper-V vms?
I'm running inside a VMWare VM.
-----Original Message----- From: "Michael Friis" notifications@github.com Sent: 5/16/2017 6:31 PM To: "docker/for-win" for-win@noreply.github.com Cc: "Jonathan Allen" grauenwolf@gmail.com; "Mention" mention@noreply.github.com Subject: Re: [docker/for-win] Windows 10 Quick Start: Failure in a Windowssystem call: winapi error #3757047808 (0xdff00000) (#743)
@alexsab1 are you running on bare metal or in some sort of VM? @Grauenwolf it looks like Hyper-V is not working on your system - can you create normal Hyper-V vms? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@friism Running on bare metal
@Grauenwolf please create your own issue for the error you are receiving. Thank you
@alexsab1 did you ever find a solution to this problem? I'm still experiencing this
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
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
Expected behavior
Run example from Microsoft article: https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10
docker run -it microsoft/nanoserver cmd
Actual behavior
Error when running example command line
Information
Steps to reproduce the behavior
Run step 4 in article: https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10