You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minetest 5.9.0-dev-fe6da3a16-dirty (Linux)
Using LuaJIT 2.1.1716656478
Built by GCC 14.1
Running on Linux/6.9.5-arch1-1 x86_64
BUILD_TYPE=Release
RUN_IN_PLACE=1
USE_CURL=1
USE_GETTEXT=1
USE_SOUND=1
STATIC_SHAREDIR="."
STATIC_LOCALEDIR="locale"
Irrlicht device
No response
Operating system and version
Arch Linux x86_64
CPU model
Intel i7-10510U (8) @ 4.900GHz
GPU model
Intel CometLake-U GT2 [UHD Graphics]
Active renderer
No response
Summary
Steps to reproduce
1 - Fork in other repository
2 - Upload git repository forked in Back3App or run docker build . minetest
3 - Wait for Back4App run docker image or run manually typing in terminal docker run -it minetest
The text was updated successfully, but these errors were encountered:
From what I can see so far: Whatever you're using to invoke Minetest ("back3app"? "back4app"?) is just passing a wrong command line: Looking at your screenshot, apparently running something like minetestserver --config /etc/minetest/minetest.conf. Minetest is just appropriately complaining about you not telling it which game to run.
Our documentation on this is lacking but I think to successfully use the docker image it should suffice if you bind mount a game to the right location in /var/lib/minetest/.minetest/games/, for example: -v /real/path/to/minetest_game:/var/lib/minetest/.minetest/games/minetest_game
Minetest version
Irrlicht device
No response
Operating system and version
Arch Linux x86_64
CPU model
Intel i7-10510U (8) @ 4.900GHz
GPU model
Intel CometLake-U GT2 [UHD Graphics]
Active renderer
No response
Summary
Steps to reproduce
1 - Fork in other repository
2 - Upload git repository forked in Back3App or run docker build . minetest
3 - Wait for Back4App run docker image or run manually typing in terminal docker run -it minetest
The text was updated successfully, but these errors were encountered: