Windows Containers don't run on latest Edge build until Experimental Features turned off

[mle-ii]

Expected behavior

Container should run and return the ipconfig info.

Actual behavior

docker daemon reports failure to find file specified and container does not run.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  26225886-548B-48BA-8935-9DCA7139122B/2017-10-26_11-48-15

• host distribution and version (Windows version, build number, etc)

Version: 17.10.0-ce-win36 (13788)
Channel: edge
Sha1: 08e31d91f902cfcff837961c8261b20a432c99db
Started on: 2017/10/26 11:15:26.812
Resources: C:\Program Files\Docker\Docker\Resources
OS: Windows 10 Pro
Edition: Professional
Id: 1709
Build: 16299
BuildLabName: 16299.15.amd64fre.rs3_release.170928-1534

Steps to reproduce the behavior

C:\Windows\System32>docker run -ti microsoft/nanoserver ipconfig /all
Unable to find image 'microsoft/nanoserver:latest' locally
latest: Pulling from microsoft/nanoserver
bce2fbc256ea: Download complete
b0b5e40cb939: Download complete
docker: Error response from daemon: open \\.\pipe\docker_engine_windows: The system cannot find the file specified.
See 'docker run --help'.

If I turn off the "Experimental Feature" via the settings it works as expected.

More issues. I turned the "Experimental Feature" setting back on to give more info and now I get a different error when running the command above, I never turned the LCOW feature back on.

C:\Windows\System32>docker run -ti microsoft/nanoserver ipconfig /all
docker: Error response from daemon: failed to get digest sha256:302c09e127848a80bad672f29e5e6263d00fa08aa4de3e4ae7a8fdb2025516bb: open C:\ProgramData\Docker\image\lcow\imagedb\content\sha256\302c09e127848a80bad672f29e5e6263d00fa08aa4de3e4ae7a8fdb2025516bb: The system cannot find the file specified.
See 'docker run --help'.

[mle-ii]

Some additional info that I had as per getting the box back into a "clean" state for testing a networking issue I ran into.
#1166 (comment)

Also, with the "Experimental Features" still on I tried turning on the LCOW and then turning it back off to see if that reset something. It still complained about the LCOW file location and I couldn't get back to the original error message.

Turning off "Experimental Features" got it back to the working state again.

[mle-ii]

Forgot to mention, going back a ways (cannot recall which version) I didn't get these errors. I spent too much time getting the network issue and this fixed so I don't have time yet to go back and figure out which version it was.

Also, this same issue occured with other instances of recent versions of docker as well, all going away once I changed it to not have "Additional Features" turned on.

[docker-robott]

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

[docker-robott]

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