itzg / itzg/docker-minecraft-bedrock-server
Network Port Occupied
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
Just pulled the docker image however when I launch the container I am having an issue with the "network port occupied".
minecraft | time="2019-09-05T09:27:15-04:00" level=debug msg="Using /data to match uid and gid"
minecraft | time="2019-09-05T09:27:15-04:00" level=debug msg="Resolved UID=1000 from match path"
minecraft | time="2019-09-05T09:27:15-04:00" level=debug msg="Resolved GID=1001 from match path"
minecraft | time="2019-09-05T09:27:15-04:00" level=debug msg="failed to read stdin" error=EOF
minecraft | Starting Bedrock server...
minecraft | NO LOG FILE! - setting up server logging...
minecraft | [2019-09-05 09:27:16 INFO] Starting Server
minecraft | [2019-09-05 09:27:16 INFO] Version 1.12.1.1
minecraft | [2019-09-05 09:27:16 INFO] Session ID 38380653-3312-4b55-b975-08139ed45610
minecraft | [2019-09-05 09:27:16 INFO] Level Name: Bedrock level
minecraft | [2019-09-05 09:27:16 INFO] Game mode: 1 Creative
minecraft | [2019-09-05 09:27:16 INFO] Difficulty: 1 EASY
minecraft | [2019-09-05 09:27:18 INFO] IPv4 supported, port: 0
minecraft | [2019-09-05 09:27:18 INFO] IPv6 supported, port: 0
minecraft | [2019-09-05 09:27:18 ERROR] Network port occupied, can't start server.
minecraft | Quit correctly
Contributor guide
Research direction
No source file or test is identified in the issue. Start by reproducing the container launch and checking its Docker port configuration against the Bedrock server's reported port; done means identifying and documenting a configuration or runtime fix that lets the server start without the network-port error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100