The LinuxServer.io team brings you another container release featuring :-
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Discord - realtime support / chat with the community and the team.
- IRC - on freenode at
#linuxserver.io
. Our primary support channel is Discord. - Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Podcast - on hiatus. Coming back soon (late 2018).
linuxserver/minetest
Minetest (server) is a near-infinite-world block sandbox game and a game engine, inspired by InfiniMiner, Minecraft, and the like.
Supported Architectures
Our images support multiple architectures such as x86-64
, arm64
and armhf
. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling linuxserver/minetest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture | Tag |
---|---|
x86-64 | amd64-latest |
arm64 | arm64v8-latest |
armhf | arm32v6-latest |
Usage
Here are some example snippets to help you get started creating a container.
docker
docker create \
--name=minetest \
-e PUID=1001 \
-e PGID=1001 \
-e TZ=Europe/London \
-p 30000:30000/udp \
-v <path to data>:/config/.minetest \
--restart unless-stopped \
linuxserver/minetest
docker-compose
Compatible with docker-compose v2 schemas.
---
version: "2"
services:
minetest:
image: linuxserver/minetest
container_name: minetest
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/London
volumes:
- <path to data>:/config/.minetest
ports:
- 30000:30000/udp
mem_limit: 4096m
restart: unless-stopped
Parameters
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.
Parameter | Function |
---|---|
-p 30000/udp |
Port Minetest listens on. |
-e PUID=1001 |
for UserID - see below for explanation |
-e PGID=1001 |
for GroupID - see below for explanation |
-e TZ=Europe/London |
Specify a timezone to use EG Europe/London. |
-v /config/.minetest |
Where minetest stores config files and maps etc. |
User / Group Identifiers
When using volumes (-v
flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID
and group PGID
.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1001
and PGID=1001
, to find yours use id user
as below:
$ id username
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
Application Setup
You can find the world maps, mods folder and config files in /config/.minetest.
Client and server must be the same version, please browse the tags here to pull the appropriate version for your server:
https://hub.docker.com/r/linuxserver/minetest/tags
Support Info
- Shell access whilst the container is running:
docker exec -it minetest /bin/bash
- To monitor the logs of the container in realtime:
docker logs -f minetest
- container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' minetest
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/minetest
Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Via Docker Run/Create
- Update the image:
docker pull linuxserver/minetest
- Stop the running container:
docker stop minetest
- Delete the container:
docker rm minetest
- Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your
/config
folder and settings will be preserved) - Start the new container:
docker start minetest
- You can also remove the old dangling images:
docker image prune
Via Docker Compose
- Update the image:
docker-compose pull linuxserver/minetest
- Let compose update containers as necessary:
docker-compose up -d
- You can also remove the old dangling images:
docker image prune
Versions
- 14.01.19: - Add pipeline logic and multi arch.
- 08.08.18: - Rebase to alpine 3.8, build from latest release tag instead of master.
- 03.01.18: - Deprecate cpu_core routine lack of scaling.
- 08.12.17: - Rebase to alpine 3.7.
- 30.11.17: - Use cpu core counting routine to speed up build time.
- 26.05.17: - Rebase to alpine 3.6.
- 14.02.17: - Rebase to alpine 3.5.
- 25.11.16: - Rebase to alpine linux, move to main repo.
- 27.02.16: - Bump to latest version.
- 19.02.16: - Change port to UDP, thanks to slashopt for pointing this out.
- 15.02.16: - Make minetest app a service.
- 01.02.16: - Add lua-socket dependency.
- 06.11.15: - Initial Release.