itzg / itzg/docker-minecraft-server
Stopping a NanoLimbo server doesn't seem to work
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 14.3k
- Forks
- 1.9k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 31
Description
Discussed in https://github.com/itzg/docker-minecraft-server/discussions/1294
Originally posted by BBaoVanC January 22, 2022
I'm not sure whose end this is an issue on, but I have a NanoLimbo server running which doesn't stop with docker compose stop until it gets SIGKILLed. NanoLimbo doesn't seem to support rcon, but it does stop when sending ctrl-c while running. How can I get it to stop on demand?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked discussion and reproducing the behavior with NanoLimbo under Docker Compose. Compare docker compose stop, the SIGKILL fallback, and NanoLimbo's Ctrl-C shutdown; done means the server stops on demand without requiring SIGKILL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100