itzg / itzg/docker-minecraft-bedrock-server
How to get the latest version of 1.20.x.y ?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
According to the document at https://hub.docker.com/r/itzg/minecraft-bedrock-server:
```
VERSION (LATEST) : can be set to a specific server version or the following special values can be used:
LATEST : determines the latest version and can be used to auto-upgrade on container start
PREVIOUS : uses the previously maintained major version. Useful when the mobile app is gradually being upgraded across devices
1.11 : the latest version of 1.11
1.12 : the latest version of 1.12
1.13 : the latest version of 1.13
1.14 : the latest version of 1.14
1.16 : the latest version of 1.16
```
Does the document mean that if you specify `VERSION: 1.20` it will get the latest version of 1.20 for example `1.20.81.01` (according to https://minecraft.wiki/w/Bedrock_Dedicated_Server#Release_versions)?
But I get this error:
```
bedrock | Downloading Bedrock server version 1.20 ...
bedrock | curl: (22) The requested URL returned error: 404
bedrock |
bedrock | ERROR failed to download from https://minecraft.azureedge.net/bin-linux/bedrock-server-1.20.zip
bedrock | Double check that the given VERSION is valid
```
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 VERSION section in the Docker Hub documentation and compare its stated values with the download request shown in the issue. Check how VERSION=1.20 is interpreted and whether the documented behavior matches the server download endpoint. Done means the documentation clearly explains the supported version syntax and gives a valid example for selecting the latest 1.20.x.y release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100