This docker image provides a Tekkit Legend (Minecraft) Server that will automatically download the latest stable
version at startup.
To simply use the latest stable version, run
docker run -d -p 25565:25565 -v /opt/tekkit:/opt/tekkit --name mc rizbe/tekkit-legend
With the -v flag, you're creating a data volume, this means that the minecraft files will be
accessible to your local machine. For data volumes in Docker, it's typically
-v someplace/opt/tekkit, for my example, I made the directory tekkit in /opt.
The advantage of doing this means that your data will always be persistent. If you delete the
mc container and make a new one, all your minecraft files will be intact. This allows you to
upgrade, make changes to your server and etc.
Where the standard server port, 25565, will be exposed on your host machine.
If you want to serve up multiple Minecraft servers or just use an alternate port,
change the host-side port mapping such as
docker run -p 25566:25565 ...
will serve your Minecraft server on your host's port 25566 since the
-p syntax is
Speaking of multiple servers, it's handy to give your containers explicit names using
--name, such as
docker run -d -p 25565:25565 --name mc rizbe/tekkit-legend
With that you can easily view the logs, stop, or re-start the container:
docker logs -f mc ( Ctrl-C to exit logs action ) docker stop mc docker start mc
Interacting with the server
In order to attach and interact with the Minecraft server, add
-it when starting the container, such as
docker run -d -it -p 25565:25565 --name mc rizbe/tekkit-legend
With that you can attach and interact at any time using
docker attach mc
and then Control-p Control-q to detach.
Might be a issue with write access to /opt, that's usually locked down. Give docker the ability to r,w,x and it should work.
I am trying to run this on my Synology NAS, everything works great apart from the mounting of an external data volume.
I have added the variable to mount /docker/tekkit to /opt from the GUI of docker and when starting for the first time the tekkit folder is created withing the share but no files are then placed there subsequently and looking at the logs/terminal the container is loading from opt/tekkit but still within the container (if that makes sense). Any ideas as to why it would not be creating all the server files in the correct folder?