Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--gameid not set on docker #14768

Open
anliben opened this issue Jun 21, 2024 · 3 comments
Open

--gameid not set on docker #14768

anliben opened this issue Jun 21, 2024 · 3 comments
Labels
@ Build CMake, build scripts, official builds, compiler and linker errors Possible close Question

Comments

@anliben
Copy link

anliben commented Jun 21, 2024

Minetest version

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

image

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

@anliben anliben added the Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible label Jun 21, 2024
@wsor4035 wsor4035 added the @ Build CMake, build scripts, official builds, compiler and linker errors label Jun 21, 2024
@appgurueu
Copy link
Contributor

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.

@sfan5
Copy link
Member

sfan5 commented Jun 23, 2024

That's a misunderstanding, the command line comes from our Dockerfile:

minetest/Dockerfile

Lines 81 to 82 in 9ab4478

ENTRYPOINT ["/usr/local/bin/minetestserver"]
CMD ["--config", "/etc/minetest/minetest.conf"]

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

@anliben
Copy link
Author

anliben commented Jun 23, 2024

I solved the problem by assigning a path to the volume, as it is apparently mandatory. Appreciate it

@sfan5 sfan5 added Question and removed Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@ Build CMake, build scripts, official builds, compiler and linker errors Possible close Question
Projects
None yet
Development

No branches or pull requests

4 participants