search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 289 forks source link

Docker for windows pull gets vmbus.dll error. #1692

Closed ghost closed 6 years ago

ghost commented 6 years ago

Expected behavior

when doing this: docker pull scentsy/dev-iis:latest in a powershell script in administrator mode, this error is thrown: Attempting next endpoint for pull after error: failed to register layer: re-exec error: exit status 1: output: remove \?\C:\ProgramData\Docker\windowsfilter\8417c373b9405faf0445b9164825969331ec72adb4b2a0648dc7c17b2ed231f4\UtilityVM\Files\Windows\System32\DriverStore\FileRepository\wvmbus.inf_amd64_9afa303f69d7201e\vmbuspipe.dll: Access is denied.

It looks like access is denied because the file was previously deleted.

Actual behavior

File should exist or not be previously deleted.

Information

This is the procmon line where it’s happening. Procmon output is also attached. It looks like it’s happening while dockerd.exe is working with it. ProcessMonitordocker vmbus issue.xlsx

vmbus error in procmon

This is the actual executed command that tried to make the delete: C:\Program Files\Docker\Docker\Resources\dockerd.exe docker-windows-write-layer C:\ProgramData\Docker\windowsfilter 85aba28bb8da61cd7c210af6d16d6a5e306f4b9fa035e8bf53b16202476b9028 C:\ProgramData\Docker\windowsfilter\48b29d2b8c8deca255ce59511fe31c99c097458971ecb704311839daa9192cdc

And here’s the stack: 0 FLTMGR.SYS FltDecodeParameters + 0x19d2 0xfffff80f5a377852 C:\WINDOWS\System32\drivers\FLTMGR.SYS 1 FLTMGR.SYS FltDecodeParameters + 0x1578 0xfffff80f5a3773f8 C:\WINDOWS\System32\drivers\FLTMGR.SYS 2 FLTMGR.SYS FltDecodeParameters + 0x117b 0xfffff80f5a376ffb C:\WINDOWS\System32\drivers\FLTMGR.SYS 3 FLTMGR.SYS FltDecodeParameters + 0xf1e 0xfffff80f5a376d9e C:\WINDOWS\System32\drivers\FLTMGR.SYS 4 ntoskrnl.exe IofCallDriver + 0x59 0xfffff803760a42d9 C:\WINDOWS\system32\ntoskrnl.exe 5 ntoskrnl.exe ExAllocatePoolWithQuotaTag + 0x51a 0xfffff803760aaada C:\WINDOWS\system32\ntoskrnl.exe 6 ntoskrnl.exe ExAllocatePoolWithQuotaTag + 0x42c 0xfffff803760aa9ec C:\WINDOWS\system32\ntoskrnl.exe 7 ntoskrnl.exe NtSetInformationFile + 0x6a7 0xfffff803760a7507 C:\WINDOWS\system32\ntoskrnl.exe 8 ntoskrnl.exe setjmpex + 0x8fc3 0xfffff80376212203 C:\WINDOWS\system32\ntoskrnl.exe 9 ntdll.dll NtSetInformationFile + 0x14 0x7ffebfb70354 C:\Windows\System32\ntdll.dll 10 KernelBase.dll DeleteFileW + 0x161 0x7ffebc1ee251 C:\Windows\System32\KernelBase.dll 11 KernelBase.dll DeleteFileW + 0xb 0x7ffebc1ee0fb C:\Windows\System32\KernelBase.dll 12 dockerd.exe dockerd.exe + 0x5f55e 0x45f55e C:\Program Files\Docker\Docker\resources\dockerd.exe

Steps to reproduce the behavior

docker pull scentsy/dev-iis:latest Error thrown on from powershell script run in admin mode.

ebriney commented 6 years ago

Hi @kriskomar-scentsy Can you try to delete layers with https://github.com/jhowardmsft/docker-ci-zap/raw/master/docker-ci-zap.exe and retry to pull. Alternatively, you can install edge version and reset to default (it includes ci-zap similar code path)

ghost commented 6 years ago

@ebriney I have the edge version. How do I reset to default?

ghost commented 6 years ago

It was determined that because my corporate network was blocking port 3544, for some reason the pull would fail somewhere in the middle. If anyone else comes across this, have your network guy make sure port 3544 is totally open.

docker-robott commented 3 years ago

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