Closed Kalmalyzer closed 3 years ago
There is no reasonable way to not make UE4Editor-Cmd load those DLLs. The only feasible way (without source code changes) is to inject the missing DLLs from Windows Server host OS into the Windows Server Core container when building the container.
After doing this, UE4Editor-Cmd can cook Win64 example game content successfully. The image size doesn't go up noticeably since the container image is still based on Windows Server Core.
The root problem is likely that those DLLs expect (directly or indirectly) some 3D related DLLs to exist in the Windows installation. Those DLLs are present in Windows Server, but not in Windows Server Core.
Typical trace:
Is there a way to make UE4Editor-Cmd not load those DLLs at startup?
-nullrhi
on the command line made no difference. Alternatively, perhaps it is possible to inject the missing DLLs (from Windows Server) into the container, just to make Unreal capable of loading those DLLs?(A third option would be to change to using Windows Server as the base image, but that might lead to other problems, like longer image pull times, longer pod startup times, etc, with no clear path for speeding things up in the future)