Untrackable Error When Fetching UE5

Output of the ue4-docker info command:

ue4-docker version:         0.0.98 (latest available version is 0.0.98)
Operating system:           Windows 10 Pro (Build 22000.675)
Docker daemon version:      20.10.14
NVIDIA Docker supported:    No
Maximum image size:         400GB
Available disk space:       40.9 GiB
Total system memory:        31.9 GiB physical, 13.5 GiB virtual
CPU:                        10 physical, 20 logical (Intel64 Family 6 Model 165 Stepping 5, GenuineIntel)

Hello there I’m having following error while executing below command : ue4-docker build custom:5.0.2 -repo="https://github.com/EpicGames/UnrealEngine/" -branch="ue5-main" --exclude debug --exclude templates --exclude ddc Do I make something wrong?

Sending build context to Docker daemon 15.36kB Step 1/18 : ARG BASEIMAGE Step 2/18 : ARG DLLSRCIMAGE Step 3/18 : FROM ${DLLSRCIMAGE} as dlls —> a5fdde4dddaf Step 4/18 : FROM ${BASEIMAGE} as deduplication —> 7c569352fed3 Step 5/18 : SHELL [“cmd”, “/S”, “/C”] —> Using cache —> 104e0c167c55 Step 6/18 : LABEL com.adamrehn.ue4-docker.sentinel=“1” —> Using cache —> 885e65c9ecc3 Step 7/18 : COPY --from=dlls C:\Windows\System32\avicap32.dll C:\Windows\System32\avifil32.dll C:\Windows\System32\avrt.dll C:\Windows\System32\d3d10warp.dll C:\Windows\System32\D3DSCache.dll C:\Windows\System32\dsound.dll C:\Windows\System32\dxva2.dll C:\Windows\System32\glu32.dll C:\Windows\System32\ksuser.dll C:\Windows\System32\mf.dll C:\Windows\System32\mfcore.dll C:\Windows\System32\mfplat.dll C:\Windows\System32\mfplay.dll C:\Windows\System32\mfreadwrite.dll C:\Windows\System32\msacm32.dll C:\Windows\System32\msdmo.dll C:\Windows\System32\msvfw32.dll C:\Windows\System32\opengl32.dll C:\Windows\System32\ResampleDMO.dll C:\Windows\System32\ResourcePolicyClient.dll C:\GatheredDLLs
—> Using cache —> 56ed15c4e544 Step 8/18 : COPY remove-duplicate-dlls.ps1 C:\remove-duplicate-dlls.ps1 —> Using cache —> 6b9e20062a38 Step 9/18 : RUN powershell -ExecutionPolicy Bypass -File C:\remove-duplicate-dlls.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. —> Using cache —> 34e1fa08b3f7 Step 10/18 : FROM ${BASEIMAGE} as prerequisites —> 7c569352fed3 Step 11/18 : SHELL [“cmd”, “/S”, “/C”] —> Using cache —> 104e0c167c55 Step 12/18 : COPY --from=deduplication C:\GatheredDlls\ C:\Windows\System32
—> Using cache —> e9b2ee901373 Step 13/18 : LABEL com.adamrehn.ue4-docker.sentinel=“1” —> Using cache —> e06ecb0cd94f Step 14/18 : RUN reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem /v LongPathsEnabled /t REG_DWORD /d 1 /f && 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 —> 80ffcc34d009 Step 15/18 : RUN powershell -NoProfile -ExecutionPolicy Bypass -Command “Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; 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 843ac16d0015 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.1.0. Downloading https://community.chocolatey.org/api/v2/package/chocolatey/1.1.0 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 “Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; 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:ltsc2022-vs2017”.

[jonpas]

Your environment’s Visual Studio doesn’t matter, ue4-docker builds inside a Docker container and installs its own Visual Studio. VS2017 is the default, but you can also select VS2019 with --visual-studio=2019. VS2022 doesn’t work yet due to issues in the engine.

[TBBle]

On Windows 11, apparently HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName is “Windows 10 Pro”, similarly to how it’s 10.0.X.Y, to not break software that has been parsing those keys/values and is looking for ‘Windows 10’ for whatever reason.

As for this issue, as noted in #230 and #216, this appears to be an issue with Windows Server 2022 images on Windows 11, that Microsoft have acknowledged but not given any useful feedback on. Although since this one’s happening on an Intel CPU, it might be different again. It’s not something ue4-docker controls, it’s something (most-likely) at the OS level or possibly container level.

On a separate note, you’re building for Visual Studio 2017, but UE5 only supports Visual Studio 2019. It’s not related to this issue, but will bite you later.