itzg / itzg/docker-minecraft-bedrock-server
Server crash on mac mini m4 after a few minutes
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
Hi,
I tried this as Docker Compose:
```
services:
minecraft:
image: itzg/minecraft-bedrock-server
environment:
EULA: "TRUE"
VERSION: "1.21.131.1"
ports:
- "19132:19132/udp"
volumes:
- xxx:/data
stdin_open: true
tty: true
```
with server.properties(only the non-default values):
```
force-gamemode=true
online-mode=false
view-distance=12
tick-distance=4
content-log-file-enabled=true
content-log-console-output-enabled=true
```
and it always crashes after a few minutes' normal play(with a switch client).
console output:
```
[2026-01-06 03:16:40:117 INFO] Starting Server
[2026-01-06 03:16:40:118 INFO] Version: 1.21.131.1
[2026-01-06 03:16:40:118 INFO] Session ID: f169eef6-3aa5-4b83-8680-fcaf1362e9f8
[2026-01-06 03:16:40:118 INFO] Build ID: 39746295
[2026-01-06 03:16:40:118 INFO] Branch: r/21_u13
[2026-01-06 03:16:40:118 INFO] Commit ID: 3c929d6fc41f48b65a9ff77078f269f25e6c9b9b
[2026-01-06 03:16:40:118 INFO] Configuration: Publish
[2026-01-06 03:16:40:122 INFO] Level Name: xxx
[2026-01-06 03:16:40:127 INFO] No CDN config file found at: cdn_config.json for dedicated server
[2026-01-06 03:16:40:128 INFO] Game mode: 0 Survival
[2026-01-06 03:16:40:128 INFO] Difficulty: 0 PEACEFUL
[2026-01-06 03:16:40:135 INFO] Content logging to console is enabled.
[2026-01-06 03:16:40:780 INFO] Content logging to disk is enabled. Writing log to: ContentLog2026-01-06_03-16-40
[2026-01-06 03:16:40:787 INFO] Opening level 'worlds/xxx/db'
[2026-01-06 03:16:41:677 INFO] Pack Stack - None
[2026-01-06 03:16:45:130 INFO] IPv4 supported, port: 19132: Used for gameplay and LAN discovery
[2026-01-06 03:16:45:130 INFO] IPv6 supported, port: 19133: Used for gameplay
[2026-01-06 03:16:45:235 INFO] Server started.
[2026-01-06 03:16:45:238 INFO] ================ TELEMETRY MESSAGE ===================
[2026-01-06 03:16:45:238 INFO] Server Telemetry is currently not enabled.
[2026-01-06 03:16:45:238 INFO] Enabling this telemetry helps us improve the game.
[2026-01-06 03:16:45:238 INFO]
[2026-01-06 03:16:45:238 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[2026-01-06 03:16:45:238 INFO] to the server.properties file in the handheld/src-server directory
[2026-01-06 03:16:45:238 INFO] ======================================================
[2026-01-06 03:22:28:402 INFO] Player connected: xxx, xuid: xxx
[2026-01-06 03:22:35:843 INFO] Player Spawned: xxx xuid: xxx, pfid: xxx
[2026-01-06 03:26:29:102 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.21.131.1
OS: Linux
Server start: 2026-01-06 03:16:40 UTC
Dmp timestamp: 2026-01-06 03:26:29 UTC
Upload Date: 2026-01-06 03:26:29 UTC
Session ID: f169eef6-3aa5-4b83-8680-fcaf1362e9f8
Commit hash: 3c929d6fc41f48b65a9ff77078f269f25e6c9b9b
Build id: 39746295
CrashReporter Key: 45cc880a-51d8-3fd3-b3f6-6189a6991469
Crash
[2026-01-06 03:26:29:103 INFO]
2026-01-06T03:26:29.153Z WARN mc-server-runner Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error. {"exitCode": 1}
2026-01-06T03:26:29.154Z INFO mc-server-runner Done
```
It's confusing that I was not able to find any meaningful error messages or logging files within the mount path, even after enabling all the log-related configs in the property.
and with `[2026-01-06 03:16:40:780 INFO] Content logging to disk is enabled. Writing log to: ContentLog2026-01-06_03-16-40`, I'm not able to find this logging file anywhere.
Can anyone help me debug this? Thanks
Contributor guide
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
Use the supplied Docker Compose configuration and server.properties as the starting point; inspect the container's stdout/stderr and the mounted /data path while reproducing the crash. Done means identifying why the Bedrock server exits with code 1 on the reported setup and documenting the relevant logs or an actionable workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100