ue4-docker: ue4-docker build 4.22.2 fails with 'out of space' with new-enough Docker EE
Output of the ue4-docker info
command: See below.
I reproduced the same failure as #37 (and the troubleshooting guide) on Windows Server 2019 with Docker 18.09.5, and upgrading to Docker 18.09.6 did not fix it.
So I don’t think this is #37, unless somehow the 8GB file copy fix (moby/moby#37771) was completely excluded from the Docker EE 18.09 series, despite the release notes.
Before:
(venv) PS C:\Users\localadmin> python -m ue4docker info
ue4-docker version: 0.0.34 (latest available version is 0.0.35)
Operating system: Windows Server 2019 Standard Version 1809 (OS Build 17763.557)
Docker daemon version: 18.09.5
NVIDIA Docker supported: No
Maximum image size: 200GB
Available disk space: 677.09 GiB
Total system memory: 63.89 GiB physical, 73.39 GiB virtual
Number of processors: 20 physical, 40 logical
(venv) PS C:\Users\localadmin> docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 49
Server Version: 18.09.5
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Standard Version 1809 (OS Build 17763.557)
Architecture: x86_64
CPUs: 40
Total Memory: 63.89GiB
Name: au1-bldwin-22
ID: IN3O:ZULX:EYEV:VGNW:EE33:WOFD:FUF3:NRTO:I2NK:6WEP:CPAL:HSPL
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Upgrade per Microsoft’s documentation
(venv) PS C:\Users\localadmin> Install-Package -Name Docker -ProviderName DockerMsftProvider -Update -Force
Name Version Source Summary
---- ------- ------ -------
Docker 18.09.6 DockerDefault Contains Docker EE for use with Windows Server.
(venv) PS C:\Users\localadmin> Start-Service Docker
After:
(venv) PS C:\Users\localadmin> python -m ue4docker info
ue4-docker version: 0.0.34 (latest available version is 0.0.35)
Operating system: Windows Server 2019 Standard Version 1809 (OS Build 17763.557)
Docker daemon version: 18.09.6
NVIDIA Docker supported: No
Maximum image size: 200GB
Available disk space: 676.86 GiB
Total system memory: 63.89 GiB physical, 73.39 GiB virtual
Number of processors: 20 physical, 40 logical
(venv) PS C:\Users\localadmin> docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 49
Server Version: 18.09.6
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Standard Version 1809 (OS Build 17763.557)
OSType: windows
Architecture: x86_64
CPUs: 40
Total Memory: 63.89GiB
Name: au1-bldwin-22
ID: IN3O:ZULX:EYEV:VGNW:EE33:WOFD:FUF3:NRTO:I2NK:6WEP:CPAL:HSPL
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 28 (11 by maintainers)
@tynril I’m not currently aware of any combination of Windows/Docker version that does not exhibit this behaviour, and judging by the comments on the upstream issue that @TBBle opened, it looks like it’s still an unsolved problem. In the meantime, you can successfully build Windows container images by excluding debug symbols with the
--exclude debug
flag.The fix has gone into https://github.com/moby/moby/ (upstream for Docker Engine) and will be part of the 20.03.0 release, whenever that is.
BuildKit support for Windows containers would be excellent, I’ll be keen to see how that progresses. Combined with a fix for this problem, it’d finally provide enough parity between Linux and Windows containers to make some serious improvements to how ue4-docker builds images.