Non-Zero Code 3221226505

Output of the ue4-docker info command:

ue4-docker info
ue4-docker version:         0.0.81 (latest available version is 0.0.96)
Operating system:           Windows 10 Pro Version 2009 (OS Build 19041.1586)
Docker daemon version:      20.10.13
NVIDIA Docker supported:    No
Maximum image size:         800GB
Available disk space:       727.04 GiB
Total system memory:        63.93 GiB physical, 73.43 GiB virtual
Number of processors:       8 physical, 16 logical

Additional details:

• Are you accessing the network through a proxy server? No

Hi, I can no longer build, its been probably 6-9 months since I last did it on this machine.

ue4-docker build 4.27.2 --no-engine --exclude ddc --exclude templates --exclude debug -isolation=process
[ue4-docker build] COMMAND-LINE INVOCATION:
[ue4-docker build] ['ue4-docker', '4.27.2', '--no-engine', '--exclude', 'ddc', '--exclude', 'templates', '--exclude', 'debug', '-isolation=process']

[ue4-docker build] UNREAL ENGINE VERSION SETTINGS:
[ue4-docker build] Custom build:  No
[ue4-docker build] Release:       4.27.2
[ue4-docker build] Repository:    https://github.com/EpicGames/UnrealEngine.git
[ue4-docker build] Branch/tag:    4.27.2-release

[ue4-docker build] WINDOWS CONTAINER SETTINGS
[ue4-docker build] Isolation mode:               process
[ue4-docker build] Base OS image tag:            20H2 (host OS is Windows 10 version 2009)
[ue4-docker build] Memory limit:                 No limit
[ue4-docker build] Detected max image size:      800GB
[ue4-docker build] Directory to copy DLLs from:  C:\Windows\System32

[ue4-docker build] GENERAL SETTINGS
[ue4-docker build] Excluding the following Engine components:
[ue4-docker build] - Debug symbols
[ue4-docker build] - Derived Data Cache (DDC)
[ue4-docker build] - Template projects and samples

Retrieving the Git credentials that will be used to clone the UE4 repo
Username: alexgeek
Password:


[ue4-docker build] Building image "adamrehn/ue4-build-prerequisites:20H2"...
Sending build context to Docker daemon  1.865MB
Step 1/27 : ARG BASEIMAGE
Step 2/27 : FROM ${BASEIMAGE} AS dlls
 ---> 7dd5ec56bd76
Step 3/27 : SHELL ["cmd", "/S", "/C"]
 ---> Using cache
 ---> d18a11e7e229
Step 4/27 : LABEL com.adamrehn.ue4-docker.sentinel="1"
 ---> Using cache
 ---> ea627f02d9d7
Step 5/27 : RUN mkdir C:\GatheredDlls && echo. && echo.RUN directive complete. Docker will now commit the filesystem layer to disk. && echo.Note that for large filesystem layers this can take quite some time. && echo.Performing filesystem layer commit... && echo.
 ---> Using cache
 ---> 148bc5607dce
Step 6/27 : RUN powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && echo. && echo.RUN directive complete. Docker will now commit the filesystem layer to disk. && echo.Note that for large filesystem layers this can take quite some time. && echo.Performing filesystem layer commit... && echo.
 ---> Running in e574a97e15ac
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download.
Not using proxy.
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/1.0.1.
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/1.0.1 to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
Not using proxy.
Extracting C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall
Installing Chocolatey on the local machine
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\ContainerAdministrator\Documents\WindowsPowerShell\Microsoft.PowerShe
ll_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring Chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder
The command 'cmd /S /C powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && echo. && echo.RUN directive complete. Docker will now commit the filesystem layer to disk. && echo.Note that for large filesystem layers this can take quite some time. && echo.Performing filesystem layer commit... && echo.' returned a non-zero code: 3221226505
[ue4-docker build] Error: failed to build image "adamrehn/ue4-build-prerequisites:20H2".

[slonopotamus]

😄 Okay, let’s move discussion to #216.

[TBBle]

So I’m not convinced it’s related.

Okay.

Sorry, I wasn’t clear. I meant I thought the Stack Overflow question I found wasn’t related. The AMD-ness of this does seem like it’s related to #216, or at least weirdly-coincidental.