question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failure building in Windows Container due to missing file

See original GitHub issue

Hi!

ue4-docker version:         0.0.72 (latest available version is 0.0.72)
Operating system:           Windows 10 Pro Version 1903 (OS Build 18362.1139)
Docker daemon version:      19.03.13
NVIDIA Docker supported:    No
Maximum image size:         200GB
Available disk space:       168.46 GiB
Total system memory:        31.95 GiB physical, 41.26 GiB virtual
Number of processors:       6 physical, 12 logical

Hi I’m attempting to run the command

ue4-docker build custom:MYTAG -repo=MYREPO -branch=release

However I get a failure building with the message. I believe this is the relevant snippet of my log:

Saving local manifest to C:\UnrealEngine\Engine\Saved\BuildGraph\Build Tools Win64\Manifest.xml ERROR: Attempt to add file to temp storage manifest that does not exist (C:\UnrealEngine\cpp.hint) (see C:\UnrealEngine\Engine\Programs\AutomationTool\Saved\Logs\Log.txt for full exception trace) AutomationTool exiting with ExitCode=1 (Error_Unknown) BUILD FAILED The command ‘cmd /S /C .\Engine\Build\BatchFiles\RunUAT.bat BuildGraph -target=“Make Installed Build Win64” -script=Engine/Build/InstalledEngineBuild.xml -set:HostPlatformOnly=true -set:WithDDC=%BUILD_DDC% && del /s /q C:\UnrealEngine\LocalBuilds\InstalledDDC 2>NUL && python C:\exclude-components.py C:\UnrealEngine\LocalBuilds\Engine\Windows %EXCLUDE_DEBUG% %EXCLUDE_TEMPLATES% && 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: 1 [ue4-docker build] Error: failed to build image “adamrehn/ue4-minimal:martov-1903”

As you can see it appears to be attempting to add a file that does not appear to exist. I am not sure if this is because of my windows setup.

Do you have any idea why this is happening?

Also I am not sure how to get the full log short of piping into a file but I attached the ending section that wasn’t cropped out by the terminal. Please let me know if you can, where to retroactively find the log.

ue4-dockerlog.txt

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:13 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
tynrilcommented, Nov 23, 2020

FWIW, the error with the missing cpp.hint file was a bug in the 4.25.4 release, which was fixed on Epic’s Perforce release branch, but not on GitHub (the 4.25.4-release tag doesn’t include the fix).

This is the commit that addressed the bug in the initial 4.25.4 release: https://github.com/EpicGames/UnrealEngine/commit/84e4ea3241c294c04fdf7d8fb63f99a3109c8edd

This is a bug with UE’s build scripts themselves, rather than with the environment. Presumably, applying that patch to Engine/Build/Commit.gitdeps.xml would fix ue4-docker’s ability to build 4.25.4. Similarly, if you’re using a custom engine repo, you can backport that patch to 4.25.4 to get around the problem.

1reaction
adamrehncommented, Dec 11, 2020

I’m used to .0 releases of new Unreal Engine versions having bugs in them that subsequently get fixed, but this is definitely the first time I’ve seen the final point release of a version introduce a bug that is then left unfixed until the next .0 release. Since I always advise people to use the newest point release of any given Engine version, I’ve added a patch in commit 99ca1b0 that injects the fix from https://github.com/EpicGames/UnrealEngine/commit/84e4ea3241c294c04fdf7d8fb63f99a3109c8edd when it detects version 4.25.4 and the fix isn’t already present (so it won’t interfere with people’s own forks that already include the backport.)

I’ll tag a new release of ue4-docker that includes the new change once I’ve tested that it fixes the build issues under both Windows and Linux.

Read more comments on GitHub >

github_iconTop Results From Across the Web

You might encounter issues when using Windows Server ...
Your 32-bit application or processes running inside the container might silently fail. Cause. This issue was the result of a security change ......
Read more >
MSBuild fails to build Visual Studio Project due to missing ...
This builds fine on the local machine where the project was created but the file is missing in the docker container.
Read more >
Troubleshooting build issues - Adam Rehn Docs
This error typically occurs when the Windows pagefile size is not large enough. As stated in the Windows containers primer, there is currently...
Read more >
Docker Desktop release notes
Release notes for Docker Desktop for Mac, Linux, Windows. ... A failed spawned command when building an extension no longer causes Docker Desktop...
Read more >
Troubleshoot Tableau Server Install and Upgrade
If clicking Restart does not restart Windows, complete the installation ... Upgrade fails due to permission problems with the backup/restore file location.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found