none
re-exec error when trying to load nanoserver image

    Question

  • Hi,

    I'm trying to follow the Windows 10 Quick start guide at:

    https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/quick_start_windows_10

    However, I'm unable to load the nanoserver image. I get the following error message:

    PS C:\WINDOWS\system32> docker load -i nanoserver.tar.gz
    58684737b3d1: Loading layer [==================================================>] 358.4 MB/358.4 MB
    re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\Docker\windowsfilter\98fe43a034d9f920760581f7
    425a6da2797bb37f77d5a2229831c03301be32c5\UtilityVM: The process cannot access the file because it is being used by anoth
    er process.

    Docker version: 
    Client:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.6.3
     Git commit:   295679c
     Built:        Fri Jul 29 18:43:44 2016
     OS/Arch:      windows/amd64
    
    Server:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.6.3
     Git commit:   295679c
     Built:        Fri Jul 29 18:43:44 2016
     OS/Arch:      windows/amd64

    I've also tried multiple 1.12 versions.

    Windows version: 10.0.14393 ( build 14393.5 version 1607) The issue also occurred with earlier builds. I also noticed that the icons in the windows taskbar become white for a second right before the error appears.

    Does anyone have an idea what may cause this issue? Please let me know if more information is required.

    Friday, July 29, 2016 7:24 PM

All replies

  • Update: I noticed that the guide has been updated to use docker pull to download the nanoserver image. I've tested this but am still receiving the same error. I've tried to uncover which process is locking the file. However, Procmon only reports the system and docker are accessing any files under UtilityVM\.

    Saturday, August 06, 2016 12:12 PM
  • I've tried again on the latest preview build (14901) with the latest docker 1.13.0-dev, build 2faeebc but I still have the same problem. I've tried re-enabling the container and hyper-v features but this also didn't solve the problem. I've tried running docker in safe-mode but I get a different error in that case:

    failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\Docker\windowsfilte
    r\ad0b03c4d7c58c9eec7ea1d08cd6686bee1a11ddd9c3d05898fe851e8e054cd3\UtilityVM: The system could not find the filter speci
    fied.

    Any pointers would be greatly appreciated.

    Saturday, August 13, 2016 5:39 AM
  • What are your antivirus settings? Maybe it's possible that your antivirus is scanning the file while docker is trying to access it. Could you check if disabling your antivirus fixes this?
    Tuesday, August 23, 2016 11:07 PM
    Moderator
  • I get the same with AV enabled and disabled:-

    PS C:\WINDOWS\system32> docker pull microsoft/nanoserver
    Using default tag: latest
    latest: Pulling from microsoft/nanoserver

    cf62dbf6d334: Extracting [==================================================>] 358.4 MB/358.4 MB
    failed to register layer: re-exec error: exit status 1: output: ProcessBaseLayer C:\ProgramData\docker\windowsfilter\b32ff61b8c1d7303904064b8
    257eec7844f3fe54a19718925bc4df288642c590: The I/O operation has been aborted because of either a thread exit or an application request.

    Wednesday, August 24, 2016 2:11 PM
  • Did you disable the OpLocks feature?

    That is done with this command:

    Set-ItemProperty -Path 'HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Containers' -Name VSmbDisableOplocks -Type DWord -Value 1 -Force

    Thursday, August 25, 2016 6:48 PM
    Moderator
  • I am seeing the same error, and I have verified that the VSmbDisableOplocks key is set to 1.

    PS C:\WINDOWS\system32> docker version
    Client:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.6.3
     Git commit:   4105cff
     Built:        Mon Aug 15 18:37:46 2016
     OS/Arch:      windows/amd64

    Server:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.6.3
     Git commit:   4105cff
     Built:        Mon Aug 15 18:37:46 2016
     OS/Arch:      windows/amd64

    Thursday, August 25, 2016 8:19 PM
  • Hi, sorry for the delay. Apparently alerting was disabled.

    I had previously tried to turn my antivirus off without success. I even created exclusion rules for the docker directory. Finally I decided to completely uninstall my antivirus and this solved the problem. I'm using Norton 360 22.7.1.32. Without the antivirus, I was able to import the nanoserver image using docker 1.13.0-dev on the 10.0.14915 N/A Build 14915 insider build. Obviously this isn't a permanent solution. Where do I best report this to get it addressed?

    Friday, September 02, 2016 5:18 PM
  • Same error using  Windows 10.0.14393 N/A Build 14393 and Norton Internet Security 22.7.132.  Might want to post on Norton NIS forum.
    Saturday, October 01, 2016 1:34 AM