ue4-docker: `choco install` fails with `Exit code was '-2147023829'` on a Windows 11 host with process isolation
Output of the ue4-docker info command:
PS D:\ue4docker> ue4-docker info ue4-docker version: 0.0.94 (latest available version is 0.0.94) Operating system: Windows 10 Pro (Build 22000.376) Docker daemon version: 20.10.11 NVIDIA Docker supported: No Maximum image size: 400GB Available disk space: 6.7 TiB Total system memory: 255.83 GiB physical, 293.83 GiB virtual Number of processors: 64 physical, 128 logical
Additional details:
- Are you accessing the network through a proxy server? NO
I am running windows 11 as a host OS.
I am building using the following command: PS D:\ue4docker> ue4-docker build -username redacted -password redacted --exclude ddc -basetag ltsc2022 -isolation=process --visual-studio=2019 4.27.2
The build is failing to create the prerequisites image, when installing git from chocolatey.
ERROR: Running ["C:\ProgramData\chocolatey\lib\git.install\tools\Git-2.34.1-64-bit.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs ] was not successful. Exit code was '-1073741819'. See log for possible error messages.
I tried creating a ltsc2022 windows server container, and repeated the following command:
choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
git installed successfully during that attempt, so this does not appear to be a chocolatey issue.
I have repeated the ue4-docker build several times, and get the same result. ue4-docker build log.txt chocolatey.log
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 56 (1 by maintainers)
ue4-docker build --no-engine --no-full --exclude debug --exclude templates --monitor -basetag ltsc2022 -isolation=process 4.27.2Azure VM D8as v4 (AMD EPYC 7763)
Annoyingly enough, that Win11 VM is the exact same version as my local machine (which fails):
It seems I don’t have any local Intel machines compatible with Windows 11.
10.0.17763.2686 Windows 10 LTSC 2019 host (fully updated as of today) + 10.0.17763.2686 Docker image (this is the one you get by
ltsc2019tag as of today) + process isolation = everything works.@alexgeek WRT your 20H2 issue in #230. 20H2 is going EOL on 2022-05-10, in just a month and a half. I don’t think it worth trying to fix anything on it. Just let it go and switch to a more long-term options.
Currently supported and functional systems with process isolation:
Technically, Windows Server 2016 and Windows 10 LTSB 2016 would also work with ltsc2016 image, but ue4-docker has dropped support for them in https://github.com/adamrehn/ue4-docker/pull/187 (though you might have success with ue4-docker versions older than
v0.0.89).I spun up a win11 VM in azure to verify this isn’t machine specific, and Git will install fine in process isolation there.
Both machines have identical windows builds, both using the same stevedore version, both building the same dockerfile, one succeeds, one fails.
We are now really in the weeds, either its something specific to this box, like hardware fail, corruption of a file somewhere, or its something really weird like a cpu specific issue (im AMD, VM is xeon).
New plan: I’m fully updating my 2019 host system and re-testing everything 😄 That Feb 2020 thing could have corrupted all of my tests I did on AMD CPU in #230.
So. Exactly the same setup as in https://github.com/adamrehn/ue4-docker/issues/216#issuecomment-1007367186 (same VirtualBox 6.1.28, same Ryzen 3700X, same Docker engine, same process isolation) with the only difference: I now use Windows Server 2022 LTSC instead of Windows 11. And I do NOT reproduce neither
Exit code was '-2147023829'norExit code was '-1073741819'.My verdict: Windows 11 process isolation is broken.
Okay, I reported it as https://github.com/microsoft/Windows-Containers/issues/197