SOLVED

Problem running microsoft/nanoserver-insider:10.0.17074.1000 image

%3CLINGO-SUB%20id%3D%22lingo-sub-146104%22%20slang%3D%22en-US%22%3EProblem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146104%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20running%20Windows%20Insider%20Server%2017074%20and%20encounter%20problems%20running%20the%26nbsp%3Bmicrosoft%2Fnanoserver-insider%3A10.0.17074.1000%20Docker%20image.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDocker%20either%20shows%20an%20error%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3Edocker%20run%20microsoft%2Fnanoserver-insider%20cmd%20%2Fc%20time%0Adocker%3A%20Error%20response%20from%20daemon%3A%20container%20301cd4c7ddd50a18a4107a074885b7a66069903e5e79cc959c3a4f582a9fe418%20encountered%20an%20error%20during%20Start%3A%20failure%20in%20a%20Windows%20system%20call%3A%20The%20compute%20system%20exited%20unexpectedly.%20(0xc0370106).%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eor%20even%20crashes%20the%20machine%20with%20a%20BSOD%20Stop%20Code%3A%20%E2%80%9CTERMINAL%20SERVER%20DRIVER%20MADE%20INCORRECT%20MEMORY%20REFERENCE%E2%80%9D%2C%20What%20failed%3A%20win32k.sys%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20current%20workaround%20is%20running%20the%20nanoserver-insider%20image%20with%20hyperv%20isolation%20which%20works%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3Edocker%20run%20--isolation%20hyperv%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20cmd%20%2Fc%20date%0AThe%20current%20date%20is%3A%20Wed%2001%2F17%2F2018%20%0AEnter%20the%20new%20date%3A%20(mm-dd-yy)%20%3C%2FPRE%3E%0A%3CP%3E%3CBR%20%2F%3EThe%20windowsservercore-insider%20image%20works%20fine%20without%20hyperv%20isolation.%3CBR%20%2F%3E%3CBR%20%2F%3EMy%2017074%20VM%20runs%20in%20VMware%20Fusion%20Pro%2010.1.1%20and%20Vagrant%202.0.1.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-146104%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EContainers%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368407%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368407%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66568%22%20target%3D%22_blank%22%3E%40Patrick%20Lang%3C%2FA%3E%2C%3C%2FP%3E%3CP%3EI'm%20seeing%20this%20issue%20on%20one%20machine%20of%20Windows%2010%20pro%201809%20with%20mcr.microsoft.com%2Fwindows%2Fnanoserver%3A1809.%20The%20issue%20occurs%20in%20running%20or%20shutting%20down%20the%20image.%20Could%20you%20please%20take%20a%20look%20at%20the%20attached%20dump%20analysis%20file%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146663%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146663%22%20slang%3D%22en-US%22%3E%3CP%3EOnly%20nano%20server%20for%20me.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20updating%20the%20docs%20regarding%20the%20fault.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146628%22%20slang%3D%22en-US%22%3ERE%3A%20Problem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146628%22%20slang%3D%22en-US%22%3ERichard%20-%20does%20this%20also%20happen%20if%20you%20run%0Amicrosoft%2Fwindowsservercore-insider%20%3F%20I%20think%20this%20is%20specific%20to%20images%0Abased%20on%20microsoft%2Fnanoserver.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146626%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146626%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20reporting%20this!%20I%20checked%20it%20out%20and%20it's%20definitely%20a%20bug.%20We%20know%20what%20caused%20it%20and%20a%20fix%20will%20be%20in%20an%20upcoming%20build.%20I%20added%20this%20to%20the%20release%20notes%20for%2017074.%20It's%20a%20general%20problem%20with%20this%20build%2C%20and%20not%20specific%20to%26nbsp%3Bany%20virtualization%20platform.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146312%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20running%20microsoft%2Fnanoserver-insider%3A10.0.17074.1000%20image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146312%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20getting%20the%20same%20error%20on%20a%20new%20install%20in%20a%20Hyper-V%20VM%20running%20on%20windows%2010.%20I%20am%20trying%20different%20Docker%20Packages%20but%20they%20all%20seem%20to%20have%20the%20same%20error.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20looks%20like%20we%20may%20have%20to%20wait%20for%20a%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'm running Windows Insider Server 17074 and encounter problems running the microsoft/nanoserver-insider:10.0.17074.1000 Docker image.

 

Docker either shows an error

 

docker run microsoft/nanoserver-insider cmd /c time
docker: Error response from daemon: container 301cd4c7ddd50a18a4107a074885b7a66069903e5e79cc959c3a4f582a9fe418 encountered an error during Start: failure in a Windows system call: The compute system exited unexpectedly. (0xc0370106).

 

or even crashes the machine with a BSOD Stop Code: “TERMINAL SERVER DRIVER MADE INCORRECT MEMORY REFERENCE”, What failed: win32k.sys

My current workaround is running the nanoserver-insider image with hyperv isolation which works

 

docker run --isolation hyperv microsoft/nanoserver-insider:10.0.17074.1000 cmd /c date
The current date is: Wed 01/17/2018 
Enter the new date: (mm-dd-yy) 


The windowsservercore-insider image works fine without hyperv isolation.

My 17074 VM runs in VMware Fusion Pro 10.1.1 and Vagrant 2.0.1. 

5 Replies

I am getting the same error on a new install in a Hyper-V VM running on windows 10. I am trying different Docker Packages but they all seem to have the same error.

 

It looks like we may have to wait for a fix.

Best Response confirmed by Stefan Scherer (Occasional Contributor)
Solution

Thanks for reporting this! I checked it out and it's definitely a bug. We know what caused it and a fix will be in an upcoming build. I added this to the release notes for 17074. It's a general problem with this build, and not specific to any virtualization platform.

Richard - does this also happen if you run microsoft/windowsservercore-insider ? I think this is specific to images based on microsoft/nanoserver.

Only nano server for me.

 

Thanks for updating the docs regarding the fault.

Hi @Patrick Lang,

I'm seeing this issue on one machine of Windows 10 pro 1809 with mcr.microsoft.com/windows/nanoserver:1809. The issue occurs in running or shutting down the image. Could you please take a look at the attached dump analysis file?