itzg / itzg/docker-minecraft-server

Corrupted world on Windows 11

Open
#1,102 37 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

keep reason/external
Dominant language
Shell
Stars
14.3k
Forks
1.9k
Avg merge
2d 10h
Merged PRs (30d)
31

Description

Describe the problem

After server restart, the server world files are corrupted. Everything works well while running pure Paper server without docker and also running same container on macOS or Linux. Recreating container doesn't help anything, after server restart I'm getting the same errors.

Container definition
version: "3.8"

services:
  mc:
    image: itzg/minecraft-server:java16
    ports:
      - "25565:25565"
    environment:
      TYPE: PAPER
      VERSION: 1.17.1
      EULA: "TRUE"
      ONLINE_MODE: "FALSE"
      COPY_CONFIG_DEST: /data
    volumes:
      - ./data/mc:/data
      - ./mc:/config
Container logs

Full server log is available here https://teksusik.pl/docker.log

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied container definition, especially the ./data/mc:/data bind mount, and inspect the linked full server log. Reproduce a restart on Windows 11 and compare the resulting world files and errors with the stated macOS and Linux behavior. Done means identifying the cross-platform cause and verifying that the world survives a container restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
devops, game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.