Stop the server gracefully with Docker

[svenmauch]

Hi, thank you for maintaining this project!

I was wondering if there is a way to gracefully stop the server using docker. If I'm not mistaken, docker stop sends a SIGTERM to the container, but when inspecting the server output using docker attach it seems there is not the usual output I expect from a stopping Minecraft server (saving world, stopping server).

Am I correct in assuming that this does not stop the server gracefully? If so, would this be an issue that could be fixed by this project or should it be directed at PaperMC?

[mtoensing]

I think the server is stopped gracefully if the container is stopped or restarted. Never had an issue with that.

[svenmauch]

Thanks for the quick response! I just took another look and it seems the server does not stop gracefully. Recently build blocks are lost and the server doesn't stop by unloading plugins and kicking users with the message "server is shutting down".

I would appreciate a quick look if my compose file is missing anything important or if you have any idea what's causing the different behavior.

services:
  minecraft:
    container_name: minecraft
    image: marctv/minecraft-papermc-server:1.16
    environment:
      MEMORYSIZE: 6G
      TZ: Europe/Berlin
    volumes:
      - './minecraft-data:/data:rw'
    ports:
      - '25565:25565'
    stdin_open: true
    tty: true

I'll try and dig a bit deeper in the meantime.

[mtoensing]

The compose file looks okay.

[svenmauch]

I took a closer look and found out the server was not running as pid 1, therefore not honoring SIGKILL.

It seems this problem only occurs when pulling marctv/minecraft-papermc-server:1.16 from Docker Hub. After pulling the master branch from GitHub, everything works as expected.

Docker Hub:

GitHub:

Could there be something wrong with the prebuilt images?

[mtoensing]

The images are build on Docker Hub with GitHub as the source. Any idea what could cause this?

[mtoensing]

done. Thank you