Question Linux Dedicated Server Doesn't Seem to Load Completely in Container

Hi all,
If I build a linux dedicated server instance and run it directly on linux, It appears to make it all the way to runtime, however, deployed in a container, it does not look like it gets past the boot config posting:

Direct on Linux:

Versus deployed in a container:

Any thoughts or advice would be helpful.

 

Would someone confirm the final `UnloadTime` is either a successful result to the server coming up or a failure and it just hangs?

I have it constrained to a docker container and I see it getting to that "UnloadTime", however, from another shell, if I `netstat -an | grep 7777` (The port this server should be opening), I do not see it.

Thanks!
D

 

Running into the same problem on 2021.3. Were you able to figure it out?

 

Hey bud, Looking deeper, it could be the lack of an RPC framework in kubernetes. I was going to look into building out GRPC, but then I came across Agones, which I think will be my next step.

I'll let you know more when I get time to sit down with it.

Thanks,
D

 

Update: It's not an rpc issue blocking. It appears it's trying to reserve memory on a graphics chipset which k8s does not implicitly provide access to. So it seems "Dedicated server" and "headless server" are not entirely accurate for a Unity build.