You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
Hello,
I'm trying to help out with a new approach for docker container integration.
I made some progress so far, but i have to overcome some limitations of docker/LinuxGSM:
I use a run.sh as entrypoint and therefore i need a proper PID 1 process for the container.
Due to the fact, that gameserver start spawns the server as new process, i can't use it.
Therefor it would be perfect, if some gameserver log command would exist, that outputs the gameserver logs into the shell like gameserver debug does and runs as long as the gameserver does.
Then, the run.sh could look like this: #!/bin/bash .... su -c "gameserver start" $user su -c "gameserver log" $user
With this aproach, docker logs -f gameserver-container would flawlessly provide all the logging from the gameserver.
Cheers
The text was updated successfully, but these errors were encountered:
Hello,
I'm trying to help out with a new approach for docker container integration.
I made some progress so far, but i have to overcome some limitations of docker/LinuxGSM:
I use a run.sh as entrypoint and therefore i need a proper PID 1 process for the container.
Due to the fact, that gameserver start spawns the server as new process, i can't use it.
Therefor it would be perfect, if some gameserver log command would exist, that outputs the gameserver logs into the shell like
gameserver debug does and runs as long as the gameserver does.
Then, the run.sh could look like this:
#!/bin/bash
....
su -c "gameserver start" $user
su -c "gameserver log" $user
With this aproach, docker logs -f gameserver-container would flawlessly provide all the logging from the gameserver.
Cheers
The text was updated successfully, but these errors were encountered: