moby: Unable to run containers with LCOW on Windows 10 17063
Description
Docker run fails on Windows 10 17063 with an error like the following:
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
ca4f61b1923c: Extracting [==================================================>] 985B/985B
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: failed to register layer: failed to start service utility VM (applydiff 8b4eeacde0dc4072a5918229fbb1f72220a52e3b5467d2231850e18e841162ba): container 8b4eeacde0dc4072a5918229fbb1f72220a52e3b5467d2231850e18e841162ba_svm encountered an error during CreateContainer: failure in a Windows system call: Not enough memory resources are available to complete this operation. (0xe) extra info: {"SystemType":"container","Name":"8b4eeacde0dc4072a5918229fbb1f72220a52e3b5467d2231850e18e841162ba_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\\Program Files\\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"bootx64.efi"},"ContainerType":"linux","TerminateOnLastHandleClosed":true,"MappedVirtualDisks":[{"HostPath":"C:\\ProgramData\\Docker\\lcow\\lcow\\scratch\\8b4eeacde0dc4072a5918229fbb1f72220a52e3b5467d2231850e18e841162ba.vhdx","ContainerPath":"/tmp/scratch","CreateInUtilityVM":true,"AttachOnly":false}]}.
I have 30+ GB of free memory, so I suspect this error is incorrect.
Steps to reproduce the issue:
- Install Windows 10 insider build 17063
- ???
docker run -it --rm hello-world
Describe the results you received:
An error containing the string “failure in a Windows system call: Not enough memory resources are available to complete this operation.”
Describe the results you expected:
No error.
Additional information you deem important (e.g. issue happens only occasionally):
I have the following optional features installed which may impact the bug:
- Containers
- Hyper-V
- Windows Defender Application Guard
Output of docker version:
Client:
Version: 17.12.0-ce-rc3
API version: 1.35
Go version: go1.9.2
Git commit: 80c8033
Built: Thu Dec 14 00:39:41 2017
OS/Arch: windows/amd64
Server:
Engine:
Version: 17.12.0-ce-rc3
API version: 1.35 (minimum version 1.24)
Go version: go1.9.2
Git commit: 80c8033
Built: Thu Dec 14 00:49:52 2017
OS/Arch: windows/amd64
Experimental: true
Output of docker info:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 9
Server Version: 17.12.0-ce-rc3
Storage Driver: windowsfilter (windows) lcow (linux)
LCOW:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 17063 (17063.1000.amd64fre.rs_prerelease.171213-1610)
Operating System: Windows 10 Enterprise Insider Preview
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 47.89GiB
Name: Ziggurat
ID: TK72:ZTYN:PHJI:GSHZ:KAUW:LJKJ:VSBI:E7JO:WT33:YIKJ:VCQL:XMXA
Docker Root Dir: C:\ProgramData\Docker\lcow
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: -1
Goroutines: 28
System Time: 2017-12-20T17:50:44.268761-06:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
OS: Windows 10 Enterprise CPU: Core i7-6700k (no overclock) Memory: 48GB
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 17 (4 by maintainers)
Build 17083 released with fix:
https://blogs.windows.com/windowsexperience/2018/01/24/announcing-windows-10-insider-preview-build-17083-for-pc/#oKVCjBkohh2sLdVS.97
This is a known bug in insider builds. A fix is supposedly being checked into Windows today, but it may take a couple of flights before it is resolved in public builds [Internal ref VSO#15063222]
For the record I can’t swap off LCOW, it errors when I uncheck that option in settings (“Unable to create File System image”), but the context menu in the system tray had
Switch to Windows Containerslisted, and I can switch to them (and pull images).If you can’t switch modes, probably best to start a thread at https://forums.docker.com/c/docker-for-windows
@PatrickLang I’ve been unable to disable LCOW, it fails to start the Moby VM (“Unable to create File System Image”).
I haven’t logged an issue here (it’s submitted a number of issues through the Docker error reporting mechanism though) as I thought it’s more related to Hyper-V than Docker.
Can also confirm with my Surface Pro4.
docker versionsysteminfo