itzg / itzg/docker-minecraft-bedrock-server

Server never starts when using Docker + Volumes

Open
#171 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
1.9k
Forks
303
Avg merge
2h 26m
Merged PRs (30d)
2

Description

Trying to get a persistent volume attached so that I can use this image for hosting. When attaching to a local volume (and also a volume in Azure), it hangs on the "Downloading Bedrock server version 1.17.10.04 ..." step and never progresses.

Output from console (Azure Container Instance):
```shell
time="2021-08-04T19:05:30Z" level=debug msg="Using /data to match uid and gid"
time="2021-08-04T19:05:30Z" level=debug msg="Resolved UID=0 from match path"
time="2021-08-04T19:05:30Z" level=debug msg="Resolved GID=0 from match path"
Looking up latest version...
time="2021-08-04T19:05:30Z" level=debug msg="stdin is detached, so forwarding is disabled"
Downloading Bedrock server version 1.17.10.04 ...
```

Here's my docker-compose.yaml file:
```yaml
version: "3.4"

services:
bedrock-server:
image: itzg/minecraft-bedrock-server
volumes:
- mcdata:/data
environment:
EULA: "TRUE"
GAMEMODE: survival
DIFFICULTY: normal
domainname: "bedrock"
ports:
- "80:80"
- "19132:19132/udp"
stdin_open: true
tty: true
sysctls:
net.ipv4.ip_local_port_range: 39132 39133
deploy:
resources:
reservations:
cpus: "2"
memory: 4G

volumes:
mcdata:
driver: azure_file
driver_opts:
share_name: mcdata
storage_account_name: azurestorageaccount
```

When I remove the custom volume from this compose file, it all works as expected (in Azure and on local Docker Desktop). Thanks for the help!

Contributor guide

Open the contributing guide

Research direction

Start with the supplied docker-compose.yaml and reproduce the hang using the mcdata volume configuration, comparing it with the no-volume case. Trace the container's /data initialization and Bedrock download entry point, using the console output to locate where progress stops. Done means the server starts and completes its download with a persistent local or Azure volume.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.