Windows 11 docker desktop installed working with windows containers, so Hyper-V.
All was working fine building 2 container images, windows server and windows servercore both 2022.
My server build context was around 4G and I built that multiple times, blah blah, and I always cleaned up.
docker info yields:
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 169
Server Version: 27.3.1
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics internal l2bridge l2tunnel nat null overlay private transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 26100 (26100.1.amd64fre.ge_release.240331-1435)
Operating System: Microsoft Windows Version 24H2 (OS Build 26100.3194)
OSType: windows
Architecture: x86_64
CPUs: 28
Total Memory: 63.69GiB
Name: 9SGKBY3
ID: cec713fe-a08f-4f2f-9dce-8a01625797df
Docker Root Dir: C:\ProgramData\Docker
Debug Mode: true
File Descriptors: -1
Goroutines: 38
System Time: 2025-03-06T16:23:02.6847503-05:00
EventsListeners: 1
Labels:
com.docker.desktop.address=npipe://\.\pipe\docker_cli
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
My DD is 4.36, and I tried to install 4.39, but I think my IT department only approved 4.36 (not happy), and so I went back to 4.36 and that was when my windows server based image started crapping out with
hcsshim::ExpandScratchSize failed in Win32: The system cannot find the file specified. (0x2)
I did did docker image prune, but that didn’t change anything.
Anyone have a clue?
PS. I was working this in a scratch area and that was why my build context was so high, but I recently trimmed out all the unneeded stuff, and got it down from over 4G to 1.2G which I need to do some other work to get that down. I have a large installer that can’t add in from the URI yet.