Closed DatMayo closed 3 years ago
Looks like that code is missing, for now switch it to use ^SIGKILL
and it'll stop. There is no process code handling though, so everything will be a SIGKILL
. ^C
just falls through to the normal docker stop <id>
command, so if that doesn't correctly stop the instance it won't work.
Closing this as it is really more of an issue with the games themselves, please feel free to open a PR if there is a more appropriate signal that you can find for the instances that gets them to stop correctly.
Closing this as it is really more of an issue with the games themselves, please feel free to open a PR if there is a more appropriate signal that you can find for the instances that gets them to stop correctly.
It's not. It's an issue with container's entrypoint: https://github.com/parkervcp/images/issues/73
cc @parkervcp
Background (please complete the following information):
Describe the bug Server process won't be shutdown gracefully. This happens to all eggs whu use
^C
as stop commandTo Reproduce Steps to reproduce the behavior: Create a server that uses a SIGINT to be terminated (i.E. TeamSpeak), start & stop the server. The server process will be killed after some time
Expected behavior A clean shutdown