Running Unity editor in batch mode on Windows Server Core in Docker

I’ve got Unity 5.6.0f3 installed in my container, but I can’t get the Unity editor to launch at all. It seems to fail to run without logging anything to file or the Windows Event logs. Below is my slightly redacted docker run command. Note that I’ve also tried to run the command while attached to the container and see the issue as well.

Anyone have any ideas what might be failing?

docker run -v :d: “C:\Program Files\Unity\Editor\Unity.exe” -batchmode -nographics -quit -executeMethod -projectPath "d:" -logFile “d:\UnityLogs.txt”

This is different from the following because I’m not trying to run a headless Unity server, but Unity itself. Unity headless server on Windows Server Core (Docker) - Questions & Answers - Unity Discussions

Hi @jowitt_msft . Did you solve your issue?
I’m facing the same problem as you… no logs from Unity launch running on batchmode on docker container…

Is there any new about it? I’m trying to do the same but no luck and I’ve found your answer here. Maybe you have some progress on it.

@george_vasilchenko

Hi, can I have some information about your setup for the cloud builder?
I’m currently working on something like yours, I have started a new instance on AWS (EC2) and I download and installed a version of Unity Editor.

When I try to launch a new project, the editor crash at the loading screen, this will appear for each project then I try to open.
So I try to run Unity from the command line with the following details: “Unitypath” -batchmode -nographics -quit -projectPath “project_path” -executeMethod AssetBundleCreator.InizializeAndBuildAssetBundle -logFile “logfile_path” -modelName 174 -modelLod 2 -outputPath "assetbundler_out_path”. This mthod this time open the project correctly but keep still stuck on the attempt to load the models.

Current server setup:

OS: ubuntu 18.04
Unity Version: 2019.4
Ram: 4Gib
CPU: 2 virtual core