adamrehn / pixel-streaming-linux

Issue tracker repository for Pixel Streaming for Linux
https://adamrehn.com/articles/pixel-streaming-in-linux-containers/
22 stars 7 forks source link

LogLoad: LoadMaChecking Pak Config get stuck #18

Closed Jggggg closed 3 years ago

Jggggg commented 4 years ago

@adamrehn hi,adamrehn, The address of the project that I use is https://github.com/adamrehn/ue4-example-dockerfiles/tree/master/pixel-streaming/4.23 According to this document https://adamrehn.com/articles/pixel-streaming-in-linux-containers/#building-container-images I configured the environment But I met one problem: Screenshot from 2020-08-28 16-26-37 Screenshot from 2020-08-28 16-26-40 Screenshot from 2020-08-28 16-26-42 Screenshot from 2020-08-28 16-26-50 Screenshot from 2020-08-28 16-26-53 log.txt

Look forward to your reply,Thank you

adamrehn commented 3 years ago

Apologies for the delay in responding to this issue, I've been drowning in work over the past few months and progress on addressing my GitHub backlog has been frustratingly slow.

In multiple screenshots there I can see that you are specifying the Docker flag --network=host after the container image name, rather than before it. This will pass that as an argument to the entrypoint inside the container (which will then be ignored since it has no meaning to the Unreal Engine or its Pixel Streaming servers), rather than being recognised as a flag instructing Docker itself to use host networking mode. Correcting the placement of the flag should trigger the expected behaviour whereby all three containers are able to communicate via the host's network interface.