itzg / itzg/docker-minecraft-bedrock-server
Cannot connect to Bedrock server from client on Mac M1 (arm64)
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 302
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
Hello, thank you very much for providing this great project.
I'm currently trying to run a Bedrock server on a Mac M1 (arm64) using the itzg/docker-minecraft-bedrock-server image. I am specifying --platform linux/amd64 in order to run the container, and the server seems to start correctly without any errors in the logs.
However, I am unable to connect to the server from a Windows Minecraft client. I have already confirmed that this is not a firewall issue.
Here are the environment details and logs:
#### Host Environment
```
$ uname -m
arm64
$ docker version --format '{{.Server.Arch}}'
arm64
```
#### Run Command
```
docker run -d -it \
--platform linux/amd64 \
-e EULA=TRUE \
-p 19132:19132/udp \
-v mc-bedrock-data:/data \
itzg/minecraft-bedrock-server
```
#### Log Output (from docker logs)
```
[2025-07-28 11:42:12:588 INFO] IPv4 supported, port: 19132: Used for gameplay and LAN discovery
[2025-07-28 11:42:12:654 INFO] Server started.
```
Everything appears to be working on the surface, but the Minecraft client cannot connect to the server. I'm wondering if this might be related to platform compatibility with M1 Macs or limitations when using --platform linux/amd64.
Additionally, I could not figure out how to view the log files inside the /data volume. If there's a way to inspect those logs for more information, I'd appreciate any guidance on how to do that.
Thank you in advance for your help!
Best regards,
kureha8827
Contributor guide
Research direction
Start by reproducing the reported docker run command on a Mac M1 with --platform linux/amd64 and the 19132/udp port mapping. Inspect the docker logs output and the /data volume contents for evidence of the connection failure; done means identifying whether the issue is platform, networking, or log access and documenting a confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100