May 19 2018 12:15 PM
May 19 2018 12:15 PM
Okay, so I'm lost. I'm trying to configure a 17666 core build on a bare-metal install (old small box...HP MicroServer N40L 8GB). For a variety of reasons, I want it to be a docker host. Also would like it to run WSL (though this is lower priority).
I want to run both Linux and Windows images. So I've installed LCOW per: https://github.com/linuxkit/lcow. Changed the service to start with the --experimental flag using sc config docker binPath= ...
Now it does not run windows containers anymore:
C:\>docker run --rm hello-world
Results in a couple application event log errors from Docker (event ID 1, no message)
Running linux containers WORKS...kinda. Take forever to start. Then I get a Microsoft-Windows-Hyper-V-VmSwitch error in the event log:
Failed to connect NIC 3BC22E50-35B0-4AB2-BB29-3E0123F8596A--2C843790-853C-4D11-9E9C-A250495F8B22 (Friendly Name: ) to port (Friendly Name: ) on switch (Friendly Name: ), status = Object Name not found..
But at least the alpine image appears to function. And networking works as expected. Just really slow getting started.
Thoughts on this one? Can I get both Windows and Linux containers to work? At the same time?
May 22 2018 10:24 AM
Did you confirm that you were able to run the Windows container previously, before enabling LCOW? Alternatively, can you run the container if you disable LCOW again?
I'm wondering if your OS build matches the container build. Here is some information about using the appropriate container Image in Windows Insider Builds:
Would this work if you install Docker and enable LCOW similarly as described in the following blog post?
May 22 2018 03:24 PM
Have you tried:
docker run --isolation=hyperv --platform=windows microsoft/nanoserver-insider:10.0.17666.1000
? that will force all the flags and use a container image matching 17666.
May 22 2018 10:38 PM
Thanks to both. SO. I did get it to work temporarily. Needed the --isolation=hyperv switch for the windows containers. After that, all worked as needed. UNTIL I decided to try to do a fresh install of docker since I was still getting warnings and errors in the event log.
So I did a normal Uninstall-Package to get rid of it. Rebooted. Install-Package. Reboot. Same problem. Decide see if I can do a "cleaner" uninstall. So Uninstall-Package. Reboot. rd /s ProgramData\docker. All hell breaks loose. That windowsfilter folder is a booger. Finally got rid of it using the docker-ci-zap tool. But I think I hosed something bad when I rd'd the windowsfilter folder. 'Cause after a reinstall (and a few more uninstall/reinstall attempts) the docker service crashes whenever I try to pull a windows-based container. Downloads the container, gives me an "unexpected EOF" error, and the docker service is down. And I'm still getting the same docker warnings in the Event Viewer.
So thanks for your help. Definitely got me moving again. But I'm thinking it's time to do a clean server install. :( Maybe it'll fix the WSL problem, as well.
I guess as semi-useful feedback, this was a nearly clean install of a 2016 server (most recent updates installed) upgraded to the 17666 build. Yes. The windows containers worked in server 2016. Pretty sure they were broken immediately after the in-place upgrade (i.e., before trying to manually install LCOW).
May 23 2018 09:56 AM