This project is a simple dockerized environment in which to run a minecraft java vanilla server. The main goals vs existing solutions are simple persistence (bind mounts to easily modify+backup world and config data), keeping a slim image (alpine based, minimal layers), and easy iterability (change one URL to rebuild to build a new version or texture pack). https://hub.docker.com/repository/docker/tarfeef101/mc_java_vanilla

tarfeef101 441e3f2a7c bad link in readme 4 vuotta sitten
config 9fefdc249f first version, basic functionality 4 vuotta sitten
worlds 9fefdc249f first version, basic functionality 4 vuotta sitten
.gitignore 9fefdc249f first version, basic functionality 4 vuotta sitten
Dockerfile 9fefdc249f first version, basic functionality 4 vuotta sitten
README.md 441e3f2a7c bad link in readme 4 vuotta sitten
docker-compose.yaml 9fefdc249f first version, basic functionality 4 vuotta sitten

README.md

Dockerized Bedrock Server

This project is a simple dockerized environment in which to run a minecraft java vanilla server. The main goals vs existing solutions are simple persistence (bind mounts to easily modify+backup world and config data), keeping a slim image (alpine based, minimal layers), and easy iterability (change one URL to rebuild to build a new version or texture pack).

The Docker Hub page can be found at this link.

Anatomy

.
config/
docker-compose.yaml
Dockerfile
README.md
worlds/

config/

This directory is what will be bind-mounted into the container to house your config files. You should put your personalized, banned-ips.json, banned-players.json, ops.json, server.properties, and whitelist.json files in this directory.

docker-compose.yaml

This file is what defines the runtime state of your container. This is a very simple setup, so just ensure to select whatever port you wish to expose for your host port, and remember to keep this project in a folder mounted on a drive where you want those persisted directories to store data.

Dockerfile

The Dockerfile tries to keep the image as simple and slim as possible. A slim base image is used to reduce size, minimal packages are installed, and all RUN commands are kept into one layer to reduce size.

worlds/

This is the bind-mounted directory which will house your world data. This should be empty unless you have a pre-existing world you want to import. If you want to add resource packs, this is the place to put them.