salt
/
docker-minecraft
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
16 Commits 2 Branches 3 Tags 627 KiB
Shell 67.8%
Dockerfile 32.2%
Go to file
Salt b4fc6a2654 Merge branch 'openjdk11' of gitlab.com:rehashedsalt/docker-minecraft into openjdk11 2022-01-02 10:59:00 -06:00
.dockerignore Testing an alternative approach to the CI 2021-05-22 00:07:13 -05:00
.gitignore Create gitignore 2021-02-16 12:18:56 -06:00
.gitlab-ci.yml Testing an alternative approach to the CI 2021-05-22 00:07:13 -05:00
Dockerfile Update Forge for 1.16 2021-12-20 12:26:22 -06:00
README.md Add the ability to define a configuration repo that's also live-downloaded 2021-05-29 14:22:53 -05:00
build.sh Update Forge for 1.16 2021-12-20 12:26:22 -06:00
server.properties Initial test build. Looks like everything works 2021-04-09 16:28:17 -05:00
start-server.sh Merge branch 'openjdk11' of gitlab.com:rehashedsalt/docker-minecraft into openjdk11 2022-01-02 10:59:00 -06:00

README.md

docker-minecraft

A Dockerfile and some assorted scripts to build a Minecraft Forge server container.

Usage

Deploy as expected:

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.

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

You can access the server console in a screen session pretty easily:

docker exec -it mycontainer screen -r minecraft

Application State

For obvious reasons, you'll want to consult the documentation of any mods you have installed, but a majority of application state lives here-ish:

  • /minecraft/world

  • /minecraft/ops.json, whitelist.json, banned-ips.json, banned-players.json, etc.

  • /minecraft/logs

Environment Variables

variable description
JRE_XMX Maximum amount of heap passed to the main Minecraft process
JRE_XMS Minimum heap size passed to the main Minecraft process
FORGE_PACK_ZIP If provided, the URL to a zip or tar.gz file that contains the modpack that needs to be installed. Will be intelligently extracted into the server directory through the magic of find.
CONFIG_REPO If provided, the URI to a git repository that contains configuration to copy over top the pack. The root of the repo will be the root of the server directory.
ARGS Any additional arguments to be passed to the JVM

Useful Arguments

The following arguments may be useful to pass through $ARGS from time to time:

  • -Dfml.queryResult=confirm - Useful when confirming through world corruption

Weird Defaults

The default server.properties contains the following changes to better facilitate usage in a modded environment:

allow-flight=true
difficulty=hard
enable-command-block=true
spawn-protection=0

FAQ

Why do you download the pack at runtime?

It allows for transparent upgrades without having to build a whole new container. You may lose container consistency, but you gain simplicity in definition.

Of course, nothing prevents you from just not using this magic variable and instead FROMing this container and building your own pack.

License

MIT