Minecraft docker image stop prematurely

[jedo-tm]

Hi,

Recently my docker images stops prematurely. I have tried to investigate different causes but is unsuccessful. I am running it on a kubuntu 20.04 LTS.

• It happens with both vanilla and forge servers
• It happens with and without autopause enabled.
• I have tried to increase memory ( -e MEMORY=10G )
• I have tried to remove and re-create container.
• I have deleted and re-downloaded image.

In the most recent crash :

• I had started the docker container
• attached to the docker and left.
• After 5 idle hours I tried to connect minecraft client but was not successfull
• I looked at terminal where I had run $docker attach mcimage
• I could exit with ctrl p ctrl q, but could not stop or start the container again

[Autopause loop] No client reconnected - stopping
[12:17:21] [RCON Listener #1/INFO] [minecraft/MinecraftServer]: Rcon connection from: /127.0.0.1
[12:17:21] [RCON Client #6/INFO] [minecraft/DedicatedServer]: [Rcon: Saved the world]
[2021-09-11T12:17:21+0200] [Autopause] Pausing Java process
read escape sequence
$ docker attach mcimage

You cannot attach to a stopped container, start it first

$docker start mcimage; docker attach mcimage

Error response from daemon: driver failed programming external connectivity on endpoint mcimage (c8d56783d606cde4af32ee08a442f901f24e2aa2b838c927bafccf90720b267d): Error starting userland proxy: listen tcp 0.0.0.0:3555: bind: address already in use
Error: failed to start containers: mcimage
You cannot attach to a stopped container, start it first_
$docker stop mcimage
mcimage
$docker start mcimage; docker attach mcimage
_Error response from daemon: driver failed programming external connectivity on endpoint mcimage (c8b3104c686f18b41f6b33be39bd7dee43b7fc2578426f1e641f67e5d788900f): Error starting userland proxy: listen tcp 0.0.0.0:3555: bind: address already in use
Error: failed to start containers: mcimage
You cannot attach to a stopped container, start it first

If I log into a different docker image, I can see that the processes running are a mixture of root and minecraft user processes running and this "picture" is general for all my containers

 $ docker exec -it mcimage2

root@fa21d4b2d7f3:/data# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND\n
minecra+       1  0.1  0.0 705272  3488 pts/0    Ssl+ 17:22   0:00 mc-server-runner --stop-duration 60s java -Xms4G -Xmx4G -jar minecraft_server.1.17.1.jar
minecra+      36  0.0  0.0   7328  3784 pts/0    S+   17:22   0:00 /bin/bash /autopause/autopause-daemon.sh
minecra+      66  408 10.4 10258468 3423352 pts/0 Sl+ 17:22   2:59 java -Xms4G -Xmx4G -jar minecraft_server.1.17.1.jar
root          94  0.0  0.0   4884  2220 ?        Ss   17:22   0:00 /usr/sbin/knockd -c /tmp/knockd-config.cfg -d -i eth0
root         215  0.1  0.0   7460  4068 pts/1    Ss   17:22   0:00 bash
minecra+     234  0.0  0.0   5476   520 pts/0    S+   17:22   0:00 sleep 10
root         235  0.0  0.0   9116  3476 pts/1    R+   17:23   0:00 ps aux*root@fa21d4b2d7f3:/data#** 

Does anyone have ideas how to solve this or further troubleshoot the problem?

[alvarlagerlof]

Looking at you logs, you seem to have auto pause turned on.

You should be able to turn it off with -e ENABLE_AUTOPAUSE=FALSE