|
|
@@ -16,7 +16,7 @@ https://docs.docker.com/engine/installation/linux/linux-postinstall/
|
|
|
* Edit data/server.properties, data/ops.txt
|
|
|
* Edit data/plugins/ configurations...
|
|
|
|
|
|
-In the docker-compose.yml, set UID and GID to the numerical IDs of your current user account. Or the image will use the default values 1000 as defined the the Dockerfile.
|
|
|
+In the docker-compose.yml, set UID and GID to the numerical IDs of your current user account. The image will use the default values 1000 as defined the the Dockerfile.
|
|
|
|
|
|
## Building Image and Running
|
|
|
|
|
|
@@ -35,7 +35,7 @@ Edit docker-compose.yml file to set the port.
|
|
|
ports:
|
|
|
- "25565:25565"
|
|
|
|
|
|
-The first number is the external port that everyone connects in on, which is the default Minecraft port. The second number is the port minecraft server listens on.
|
|
|
+The first number is the external port that everyone connects in on, which is the default Minecraft port. The second number is the port the minecraft server listens on.
|
|
|
|
|
|
To use port 20065, change to:
|
|
|
|
|
|
@@ -44,7 +44,7 @@ To use port 20065, change to:
|
|
|
|
|
|
**Note: You'll need to use 20065 in the Minecraft client to this non-standard port number.**
|
|
|
|
|
|
-I don't recommend you change the Minecraft port number on the server side. There's no need to with Docker! But, if you really, really want to, here's what you'll need to update:
|
|
|
+I don't recommend you change the Minecraft port number on the server side. There's no need to with Docker! But, if you really, really want to, here's what you in for:
|
|
|
|
|
|
* Change the Minecraft port in the server.properties file
|
|
|
* Change the value following the : in the docker-compose.yml ports settings to the new port number
|
|
|
@@ -65,9 +65,11 @@ In data/server.properties set:
|
|
|
* rcon.password=mindcraft
|
|
|
* enable-rcon=true
|
|
|
|
|
|
+The shutdown message and delays are in the mc-java/launch.sh script in the save_shutdown() function. Be careful making the delays too long! Docker sends SIG_TERM, waits 10 seconds, and then sends SIG_KILL.
|
|
|
+
|
|
|
## Is it safe to enable rcon? Is this secure?
|
|
|
|
|
|
-Yes, so long as you don't expose the rcon port 25575 to the world in docker-compose.yml. If you do expose the rcon port, then you must change the rcon.password and update the docker image launch.sh script. In launch.sh change the rcon port and password information on the line starting with RCON=. Expose the rcon port by adding a line to the ports section of the docker-compose.yml.
|
|
|
+**Yes, so long as you don't expose the rcon port **25575 to the world in docker-compose.yml. If you do expose the rcon port, then you must change the rcon.password and update the docker image launch.sh script. In launch.sh change the rcon port and password information on the line starting with RCON=. Expose the rcon port by adding a line to the ports section of the docker-compose.yml.
|
|
|
|
|
|
## Running other Minecraft Servers
|
|
|
|
Steve Thielemann