Important, a question: for the current project, after packing the DS server into a Linux project file, use dockerfile to pack it into an image. Then use the pod of kubernetes to start the image. After observing, the image cannot be started successfully in pod, corresponding to CMD or ENTRYPOINT, the image is executed with the packaged Linux project startup script, and the log shows that there is no successful binding of port, such as 7777, logs are intercepted as follows :
…
[2023.06.07-02.57.03:682][ 0]LogNetCore: DDoS detection status: detection enabled: 0 analytics enabled: 0
[2023.06.07-02.57.03:682][ 0]LogInit: BSD IPv4/6: Socket queue. Rx: 262144 (config 131072) Tx: 262144 (config 131072)
When started in a container, the logs can’t go on, they end at above
[2023.06.07-02.57.03:682][ 0]LogNet: Created socket for bind address: 0.0.0.0 on port 7777
[2023.06.07-02.57.03:682][ 0]PacketHandlerLog: Loaded PacketHandler component: Engine.EngineHandlerComponentFactory (StatelessConnectHandlerComponent)
[2023.06.07-02.57.03:683][ 0]LogNet: GameNetDriver IpNetDriver_2147482551 IpNetDriver listening on port 7777 .
…
[2023.06.07-02.57.03:686][ 0]LogInit: Display: Engine is initialized. Leaving FEngineLoop::Init()
[2023.06.07-02.57.03:686][ 0]LogLoad: (Engine Initialization) Total time: 0.91 seconds
Using the script to start, you can see the full log endings shown here
The DS server can be started successfully by directly executing the startup script in the packaged Linux project file.
Currently, the integrity of the COPY file has been verified, the user’s permissions (into the pod, direct execution of the script, can successfully start the DS), so I do not know what the problem is?
Hope to get your answer, thank you very much!
This problem has been blocking me for many days！ 
