Forum Discussion
WSL and Docker and Linux oh my!! (Part 2: Docker)
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).
- Patrick LangMay 23, 2018MicrosoftAlright let us know how it goes.
--isolation=hyperv is ALWAYS needed if you're running a container that was built using a Windows base image older than the current release. That explains why containers you had on Windows Server 2016 didn't work after the upgrade to 17666. There's more details here: https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility