Closed LoockyCZ closed 1 year ago
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
It looks like you are running PaperMC? The autopause description section of the README explains you need also need to do something special for the JVM in that case.
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
I finally thought of something can be done in mc-server-runner:
I don't know how clean this solution is, but for my purposes I use this patch. https://github.com/itzg/docker-minecraft-server/commit/b49e4400aa809106449ccdafac0a6b8e65ceba68
Thanks for info. It's a decent modification but I don't like that it puts mc-server-runner in the background. It is supposed end up as PID 1 and that change defeats that.
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
I have An Error
[00:04:07] [Server thread/WARN]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
[00:04:07] [Server thread/WARN]: The server will make no attempt to authenticate usernames. Beware.
[00:04:07] [Server thread/WARN]: While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
[00:04:07] [Server thread/WARN]: To change this, set "online-mode" to "true" in the server.properties file.
[00:04:07] [Server thread/INFO]: Preparing level "world" Killed
Describe the problem
If the server has been suspended, the server will be killed when the container is stopped. The STOP_DURATION timeout occurs. If the server has not yet been suspended or is awakened, the process is correctly terminated immediately. From what I understand by reading the code docker-minecraft-server and mc-server-runner, the java process must be woken up (pkill -CONT java), otherwise the "stop" command from mc-server-runner will not be processed.
Container definition
docker-compose.yml
env.env
Container logs
Suspended server:
Unsuspended server