itzg / itzg/docker-minecraft-bedrock-server
Minecraft noob here; wanting to learn
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
Hey, first of all: bear with me. I'm a Minecraft noob :).
I'm trying to setup a simple minecraft server for my son (playing on his iOS device). So I think I need to run a bedrock instance, right?
So I tried to start a container using this: `docker run -it -v /srv/local/services/minecraft/data:/data -e EULA=TRUE -p 19132:19132/udp itzg/minecraft-bedrock-server`. All fine, container running and healthy.
But then what? When I try to connect to the instance from the iOS minecraft game, then I can't connect (by ip address:port). So first thing is trying to find out if the container is actually working fine. So -on the server- I'm trying to do a telnet:
```
rlommers@server [~]$ telnet localhost 19132
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
```
Which is a bit strange, right? docker ps outputs this:
```
8b7721640b4c itzg/minecraft-bedrock-server "/usr/local/bin/entr…" 3 minutes ago Up 3 minutes (healthy) 0.0.0.0:19132->19132/udp friendly_nobel
```
So basically my question is: how do I connect to a running instance of a bedrock server on an iOS device?
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 with the posted docker run command and docker ps output, then inspect the running container's logs and UDP port reachability. Done means identifying whether the Bedrock instance is listening correctly and documenting the connection path from the iOS client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100