-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade then Unable to create File System Image #1514
Comments
I have the same issue. I uninstalled and reinstalled and still get the same issue. This came immediately after the latest update and renders docker completely unusable on windows. |
Hi, had the same problem, seems one of the suggested solutions on possible duplicates solved the problem for me: EDITED: Seems that Windows containers work tho, switching to linux containers doesn't want to work. |
Here's my diagnostic report for this issue BE207427-6264-469F-BF62-C074E5DF5B17/2018-01-12_11-16-22 |
I am experiencing the same bug on both my laptop and my desktop PC. The main similarities is same build of Windows: 17074 |
Also seeing this same issue on build 17074. Diagnostic ID 30165A10-397B-49A0-9A53-1ACD1BB261D9/2018-01-17_12-01-35. I also cannot manually enable shared drives in the settings. Update: |
+1 on the upgrade blocking Docker from starting at all.
|
Same issue on 17074, reverted to 17025 and docker is fine. |
We have narrowed this down to something related to the IFileSystemImage. We are still looking at what change could have caused it to break but we are getting closer. |
I'm tracking this internally - MS#15594197 . Here's another example that breaks: |
If this helps another diagnostic: 24DDD2B5-0880-4E0C-8264-6A9B1AA18EC0/2018-01-24_01-41-35 |
I have this error an in the windows event logs I see |
I managed to start the MobyLinuxVM using the MobyLinux.ps1 powershell script. There was an error at line 301 because it should not use Test-Path if $confIsoFile is null / empty string. After I added a -ne "" check it works. Like this: Although the VM starts in Hyper-V the rest of Docker does not start. So it does not fix all isues. Edit: After changing to Docker Edge (17.03.0-ce-win1 (10318)) on Windows 10 Version 1709 (17074.1002) it started working again :) |
Same for me on windows 17083 C2316E66-0B1E-48AF-BC4E-36B7BE02E4EA/2018-01-24_22-22-52 |
I had the same problem with Windows 10 (Build 17083) and docker versions 17.12 and 18.01 I did the downgrade to docker 17.09.1 and workds!! https://download.docker.com/win/stable/14687/Docker%20for%20Windows%20Installer.exe |
We think the underlying Windows bug has been identified and we have a fix in review. Once the PR has been merged, verified and a target build number has been identified I will update this issue. I have requested it be fast tracked so we can flight out the fix ASAP. |
Windows 10 Build 17074. Uninstall and re-install 17.09.1 works, too. |
Latest edge release is still broken in 17083. Workaround is to use Docker Toolbox. |
It will be broken until the underlying Windows bug is resolved. There were two bugs in Windows, the first (moby/moby#35854) was fixed in 17083, this one (Unable to create File System Image) is still open. @taylorb-microsoft any updates on this? 😄 really want to play with the new built-in Kubernetes feature in Edge version. |
since 17.09.1 works, how to download this older version? |
@dogopupper You can find download links for older versions on the release notes page. However, it appears there is no link for any version over --Edit-- See the comments in the issue linked above for a Chocolatey link to |
Windows Build 17093 was released, however reports are saying that same problem persists 😢 The release notes indeed does not mention anything related to Docker... @taylorb-microsoft would you be able to tell if this build was supposed to fix this issue? |
@dannyk81 sorry, but the fix in 17093 was incomplete. You may see this error instead now, but it's still the same broken component in Windows. Docker UI will show:
You'll find a crash report in the Windows application event log:
|
Thanks @PatrickLang! |
Is the only solution to revert to an older Docker version? |
Windows 10 Pro Build 180116
Diagnostic: 073A60F1-EDDF-4F16-88FF-B04DC99ED137/2018-02-09_07-25-57 Getting this bug... Reverting as others have seems to fix it. |
Same problem on Build 17093 prerelease 180202-1400. |
Still doesn't work on new 17604 build |
@PatrickLang @taylorb-microsoft looks like 17101 & 17604 also don't have the fix, can you confirm? |
#1540 (comment) for update on workaround in D4W |
17604 is "skip ahead" and doesn't have the fix yet. Still waiting on build number for that branch. |
I am on Windows 10 Insider Slow version 1709 Build 17074.1002 and also had the error "Unable to create file system image" when I was using Docker Community Edition 17.12.0-ce-win47 2018-01-12 (Stable). |
@haroldvandekamp worked for me as well. It just needed a restart for me to function properly. Thx. |
+ 1OS: W10 Pro Insider 1709 (Build 17074.1002) diagnostic id: 7B3C5A35-F5BA-4D55-AB33-DA588E416950/2018-02-23_19-57-16 |
This is fixed in the latest fast ring build [17107] with Docker 18.02 (Edge) |
+1 latest stable build is broken latest windows. |
We have changed the mechanism by which the filesystem is created and that fix is available in both stable and edge channels. Closing |
I had this same issue on: Deleting all of the Hyper-v related network adapters using the device manager and letting Docker re-create them fixed it. |
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Docker for Windows starts after an update and doesn't say "EDGE" on the application icon.
Actual behavior
Docker for WIndows doesn't start AT ALL. Even after an uninstall and re-install. Also, the app icon says "edge"
Information
Windows 10 Pro Insider Preview 1709 Build 17063.1000
Docker: 17.12.0-ce-win46 (15048)
Steps to reproduce the behavior
Upgrade to
Error Message
Logs
The text was updated successfully, but these errors were encountered: