salt/docker-minecraft
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update the build script so it actually changes the Minecraft version

Browse Source
This commit is contained in:
Salt 2021-05-22 00:14:16 -05:00
parent 0dd98315e5
commit c7328f43c2
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -12,7 +12,7 @@ docker run -p 25565:25565 rehashedsalt/minecraft-forge:1.16.5-36.1.4-1.0.0
And badda bing, badda boom, you'll have a Minecraft Forge server of whatever the tag is. And badda bing, badda boom, you'll have a Minecraft Forge server of whatever the tag is.
For obvious reason, you **should never use the :latest tag!** The "latest" tag of each version of Minecraft is somewhere along the lines of "1.16.5-36.1.14-master". See Dockerhub for more info.
## Server Console ## Server Console

4
build.sh
View File

@ -20,7 +20,11 @@ docker buildx create --use
for mc in ${mcversions[@]}; do for mc in ${mcversions[@]}; do
forge="${forgeversions[$mc]}" forge="${forgeversions[$mc]}"
echo "Building image for Minecraft $mc, Forge $forge, CI_COMMIT_REF_NAME of $CI_COMMIT_REF_NAME" echo "Building image for Minecraft $mc, Forge $forge, CI_COMMIT_REF_NAME of $CI_COMMIT_REF_NAME"
# --no-cache is required for clean builds
docker buildx build \ docker buildx build \
--build-arg MINECRAFT_VERSION="$mc" \
--build-arg FORGE_VERSION="$forge" \
--no-cache \
--platform linux/amd64 \ --platform linux/amd64 \
--tag "$CI_HUB_USERNAME/$CI_PROJECT_NAME:$mc-$forge-${CI_COMMIT_REF_NAME:=bleeding}" \ --tag "$CI_HUB_USERNAME/$CI_PROJECT_NAME:$mc-$forge-${CI_COMMIT_REF_NAME:=bleeding}" \
--push \ --push \