itzg / itzg/docker-minecraft-bedrock-server
New /data volume prevents server startup
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
Creating a new container with a new volume, such as when starting the compose stack for the first time, does not start the server. The reason is /data is owned by root. In case of empty /data, ownership should be changed to $UID:$GID before demoting.
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
Start by inspecting the container startup and volume-initialization logic responsible for preparing /data before the process is demoted. Reproduce a first-start compose setup with a new volume, then verify that an empty /data receives the requested $UID:$GID ownership and the server starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100