docker load not working #355
Comments
|
Do you have any other images installed? I haven't seen this problem since we released put
@enderb-ms can you watch this issue? |
|
There is no other image installed. I have try it with windowsservercore but it's the same |
|
I have the same problem |
|
Any update or work around on this? I got the same error. |
|
@wangosu Have a look st the Windows 10 installation docs. It has been updated to download docker 1.13.0-dev zip file which fixes this issue. |
|
@StefanScherer I did exactly as stated in https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/quick_start_windows_10 |
|
I have try it with 1.13.0 too |
|
Still struggling at I've just spun up an empty Win10 1607 VM and installed Docker and pulled the nanoserver image and it worked fine. Details of my setup can be found in this Vagrant environment and especially in this What does |
|
My issue is docker pull, I tried both microsoft/nanoserver, microsoft/iis; after the image is extracted, both gave error:" failed to register layer; re-exec eror: exiy status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter...\UtilityVM: The process cannot access the file because |
|
I am getting exactly the same error using both 1.12.0 and 1.13.0-dev. I had Docker for Windows installed previously and it was working fine for Linus based images. But I need to run windows based apps, so I uninstalled that, installed Windows Containers and get this error for all windows images that I tried. Please help. Thank you! |
|
Here is what i found after trying different ways:
|
|
I found another thread about the same issue and someone there mentioned that it started to work after he completely removed antivirus software: https://social.msdn.microsoft.com/Forums/en-US/13523ccf-baf4-49fc-9e73-1df07e512304/reexec-error-when-trying-to-load-nanoserver-image?forum=windowscontainers |
|
VladM-L, removed the antivirus did help. It is working for me now. Thanks |
|
You are welcome wangosu! |
|
Unfortunately for me I'm also having the same issue, but uninstalling antivirus an option. Wouldn't it be better to get to the bottom of the issue rather than asking people to compromise their security? |
|
Yep - I'm hitting this error too :-( Fresh Win10 install but must run Symantec Endpoint Proctection (corporate policy). PS C:\Program Files\Docker\Docker> docker version Server: |
|
I was able to get around this by just adding a folder exclusion for "C:\ProgramData\docker" in SEP on my box. Once I did that, the temp file being locked was released, and I was able to successfully pull, extract and view the image on my box. I hope this helps out, as I agree that fully uninstalled SEP or any AV product is not a valid workaround. |
|
@aphophas I tried the same thing and it didn't help in my case, only a full uninstall did the trick unfortunately. |
|
I can confirm that Unintalling Norton fixes it. Its only the extracting that fails. If you extract and reinstall you can run the images. |
|
I can confirm that temporarily disabling BitDefender mitigated the issue. |
|
Added folder exclusions for "C:\ProgramData\docker" & "C:\ProgramData\docker". Still getting the same error: |
|
+1 for me. Tried disabling Norton, but of course is still had running processes. Had to fully uninstall it, then redid the pull and it worked. |
|
I was having this same issue. I have Symantec Endpoint Protection - and it's password protected so I can't uninstall or change its exclusions. However, the problem went away after I upgraded to Docker 1.14! https://master.dockerproject.org/windows/amd64/docker-1.14.0-dev.zip |
|
@dschilling do you have instructions or link on how to perform the upgrade? |
|
@jplonghi if you figure that out let me know please. |
|
To download the latest zip file have a look at https://msdn.microsoft.com/en-us/virtualization/windowscontainers/docker/configure_docker_daemon#manual-installation |
|
I am getting the same behavior with version 1.14 Version Client: Server: Error [16:48:51.689][WindowsDockerDaemon][Info ] time="2016-12-07T16:48:51.688867300-08:00" level=error msg="Error trying v2 registry: failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\Docker\windowsfilter\4a3cff26991a967f76d0ae1eb8daf8115632bc769df418fb1eb21f756e07f131\UtilityVM: The process cannot access the file because it is being used by another process." |
|
I had to uninstall SEP |
|
I'm getting this error when I'm using windows containers but not when using linux containers.
I'm using Kaspersky Endpoint Security 10. Tried disabling it, excluding multiple paths but still no luck. these are the logs of it not working: [11:00:32.939][WindowsDockerDaemon][Debug ] time="2017-08-04T11:00:32.938546300+01:00" msg="Calling POST /v1.30/images/create?fromImage=microsoft%2Fnanoserver&tag=latest" |
|
just an update... I've uninstalled Kaspersky Endpoint Security 10 and these are the logs of it working: [13:35:00.925][WindowsDockerDaemon][Debug ] time="2017-08-04T13:35:00.925462700+01:00" msg="Calling POST /v1.30/images/create?fromImage=microsoft%2Fnanoserver&tag=latest" |
|
I believe I've discovered a cause besides anti-virus problems. In my case, it was one particular file that was always locked: It was always that one NanoServer-Win32Compat package. Disabling antivirus had no effect. What did fix this was going to C:\Windows\Temp, and deleting every folder that began with "hcs". It looks like these folders are created by the Host Compute Service during the image creation process. They're supposed to be cleaned up at the end of the build, but mine weren't. Apparently they were holding some kind of lock, and that lock was interfering with both the extraction process, and the Temp cleanup process. I hope this info helps anyone else who has this issue! |
|
Hi @DavidHaitch! I've noticed, that the same file as you mentioned is being used by another process in my environment as well. Sometimes I've managed to get over it by killing vmcompute -process but yesterday things got so stuck up that I had to zap my whole docker folder. Now everything seems to work alright again, but the next time I'll get that error I'll try your fix. Thanks! |
|
@JanneRantala If you do see this again, try pulling microsoft/windowsservercore-insider first. That one worked for me when the regular windowsservercore did not. |
|
@DavidHaitch I'm not using insider version of Windows 10. |
|
@JanneRantala Neither am I. The windowsservercore-insider container worked nevertheless. Such is the magic of containerization. |
|
Tried adding folders to exclusions in Kaspersky, still not helping. Having to uninstall anti-virus to get Docker for Windows to work, if that does fix it, is a bit much. |
|
I have found if I stop and remove the running containers on my docker it seems to solve the issue. So I guess I need a build box that I will never run a container on it. |
|
@aphophas I am curious about this SEP exclusion for |
|
Nothing interesting works for me here. For sure, I didn't try to uninstall my SEP (corporate policy as everyone). But, disable SEP and BitLocker change nothing, always stuck to : I guess one good solution will be to add a timeout option in docker to wait for availability of the internal file ? For information I'm under the lastest stable version of Docker : |
|
FYI (@wadinj et al.) this is not Docker fault, it is There is nothing Docker can do about it. Since I wrote myself simple Go app that is just calling So if there is anything that can be fixed (or improved), it has to be done in I am currently waiting for SEP v14 upgrade, once I upgrade I'll let you know if this fixes the problem on my side. |
|
@nanoant Great analyze ! I didn't spend more time on and finally switch to Linux container with toolbox. Thanks ! |
|
I face the same issue on WS2016, and was basically because I was trying to "store" the images in the D drive. So after remove the setting "data-root": "D:\dockerimages" from the config now is working well |
|
Finally this error went away when I downloaded the edge version of Docker to replace the stable one. |
|
Have you tried to disable the compression on the folder: C:\ProgramData\Docker? Just try that, Right click ont he folder docker -> properties -> advanced -> uncheck "Compress contents to save disk space" Do it while docker is off. Thanks |
|
Happens for me too :(
Having SEP 12 here, cannot disable, upgrade or change config (corporate policy). |
|
I tried in a fresh Windows 10 Enterprise N 1709 VM and installed McAfee Endpoint Protection 10.5.3.3178. Out of the box the Running 10.5.1 elsewhere and it has this issue, not 100% if it's McAfee or some other environmental issue. |
|
Mcafee AV officially does not support docker containers, so you will get hit a miss situation in both development and production. |
|
I have the same issue: AV: Kaspersky Endpoint Security 10.3.0.6294 Temporary AV disabling didn't help. Can't remove AV because of the corporate policy. |
|
I have the same issue on Windows Server 1709 using current latest everything: I only have the built-in Windows Defender feature installed, so I tried excluding the Docker folder: Then I tried disabling Windows Defender realtime monitoring: Then I tried removing the Windows Defender feature: Finally, I tried @brunofvalli 's suggestion and I stopped all other running containers before pulling the container and it worked. Eureka! |
|
@RustyCZ You rock! I had the same problem when execute |
|
I have got the same error. |
|
i got the same problem here, running windows server 2019 with SEP 14.3 MP1, had to fully uninstall SEP for docker to run normaly |
and others
Hi,
I have try the description from
Virtualization-Documentation/virtualization/windowscontainers/quick_start/quick_start_windows_10.md
but there is a problem on Step 3
docker load -i nanoserver.tar.gzI got the following error
If I try it with docker pull it's the same:
The PowerShell ist startet as administrator.
Docker version:
Windows Insider-Build 14393.67
The text was updated successfully, but these errors were encountered: