search

linuxserver / docker-minetest

GNU General Public License v3.0
50 stars 33 forks source link

Minetest server fails to start in latest container release 5.4.1 #40

Closed adrinux closed 1 year ago

adrinux commented 2 years ago

Expected Behavior

The minetest server should start. The usual debug log is:

2022-02-02 12:49:28: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
<snipped asci art>
2022-02-02 12:49:32: ACTION[Main]: World at [/config/.minetest/worlds/world]
2022-02-02 12:49:32: ACTION[Main]: Server for gameid="minetest" listening on 0.0.0.0:30000.

Current Behavior

The minetest server loops at the automatically selecting world step, debug log sample:

2022-02-02 13:04:01: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:04: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:06: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:08: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:11: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:14: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]

Steps to Reproduce

  1. Start container via docker-compose or on the command line using the tag linuxserver/minetest which pulls the 'latest' 5.4.1 tag

Environment

OS: Manjaro Gnome kept up to date, Linux kernel 5.15.16 CPU architecture: x86_64 How docker service was installed: Docker version 20.10.12, build e91ed5707e Installed from distro community repo:

docker-compose       [Installed] 2.2.3-2                        community 
    Fast, isolated development environments using Docker
docker                       [Installed] 1:20.10.12-1                   community 
    Pack, ship and run any application as a lightweight container

Command used to create docker container (run/create/compose/screenshot)

Using this docker-compose:

version: '3.6'
services:

minetest:
  container_name: minetest
  image: linuxserver/minetest:amd64-5.4.1-ls81
  environment:
    - PUID=1000
    - PGID=1000
    - TZ=Europe/London
    - CLI_ARGS=--gameid minetest
  volumes:
    - /pool2g/appdata/minetest:/config/.minetest
  ports:
    - 30000:30000/udp
 # changed entrypoint as per:
 # https://github.com/linuxserver/docker-minetest/issues/30#issuecomment-612797819
  entrypoint: ["/usr/bin/minetestserver", "--config", "/config/.minetest/main-config/minetest.conf"]
  restart: unless-stopped

networks:
  web:
  external: true

Or using the cli

docker run -d \
  --name=minetest \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -e CLI_ARGS="--gameid minetest" \
  -p 30000:30000/udp \
  -v /pool2g/appdata/minetest:/config/.minetest \
  --restart unless-stopped \
  lscr.io/linuxserver/minetest

Docker logs

2022-02-02 13:04:01: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:04: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:06: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:08: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:11: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 13:04:14: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]

Repeats for as long as container is left running.

Notes

This is for an existing world/game. Attempts to log in from a client app result in a 'connection timed out' error. I've set the logging level to 'verbose' minetest.conf, but I'm not sure minetest is getting to the point where it reads that conf file since there is no increase in logging - at least as seen in the docker log and 'debug.txt'.

Workaround pin the tag to previous release:

~ 260     image: linuxserver/minetest:amd64-5.4.1-ls81

TODO

I should try a fresh new world/game.

github-actions[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

adrinux commented 2 years ago

Tried starting fresh...and found I'd forgotten how I set these up originally, wish I'd made notes.

Created a directory for it's volume mount and chowned it to me (puid set in compose is mine):

mkdir /pool2g/appdata/minetest-new

Created this, which complained about being unable to find the non-existant conf file so I commented out the custom entrypoint:

  minetest-new:
    container_name: minetest-new
    image: linuxserver/minetest
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /pool2g/appdata/minetest-new:/config/.minetest
    ports:
      - 30003:30000/udp
    # changed entrypoint as per:
    # 
    #entrypoint:
    # [
    #    "/usr/bin/minetestserver",
    #    "--config",
    #    "/config/.minetest/main-config/minetest.conf"
    #  ]
    restart: unless-stopped

And the server started plus created the default dirs and files. Edited the new main-config/minetest.conf to add an Admin user and restarted the container. Can't log in, still times out and still have the same error message even though things seem to start up ok:

GID/UID,
[cont-init.d] 90-custom-folders: exited 0.,[migrations] no migrations found,
[cont-init.d] 01-migrations: exited 0.,
[cont-init.d] 10-adduser: executing... ,
-------------------------------------,
         | |  ___   _    __,
         |_| |___/ |_|  \__/,
Brought to you by linuxserver.io,
         | | \__ \ | | | () |,
         | | / __| | |  /  \,
          _         (),
To support LSIO projects visit:,
https://www.linuxserver.io/donate/,
User uid:    1000,
User gid:    1000,
[cont-init.d] 10-adduser: exited 0.,
[cont-init.d] 30-config: executing... ,
[cont-init.d] 30-config: exited 0.,
[cont-init.d] 90-custom-folders: executing... ,
[cont-init.d] 99-custom-files: executing... ,
[custom-init] no custom files found exiting...,
[cont-init.d] 99-custom-files: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
2022-02-02 17:10:05: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:06: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:07: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:08: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:09: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:10: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:11: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:12: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:13: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:14: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:15: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:16: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:17: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:18: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:19: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:20: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:21: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:22: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:23: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:24: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:25: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:26: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:27: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:28: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:29: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:30: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:31: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:32: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:33: [Main]: Automatically selecting world at [/config/.minetest/worlds/world],
2022-02-02 17:10:34: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
aptalca commented 2 years ago

Your custom entrypoint is likely what broke it by bypassing all of our init scripts.

Please start over with an empty config folder, and don't add an entrypoint

adrinux commented 2 years ago

Please start over with an empty config folder, and don't add an entrypoint

That's exactly what I did, as described in 2nd comment.

Also, would the init scripts be relevant to my existing containers with already created worlds, users etc? Which is what the original report was about.

I think I tried removing the custom entry point on those too, (and recreating the containers of course) - made no difference.

Is there a chance that these images are now pulling in Minetest 5.5.0 during the build process? It was released 3 days ago.

adrinux commented 2 years ago

I can confirm:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing... 
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-02-02 17:48:16: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:16: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:17: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:17: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:18: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:18: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:19: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:19: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:20: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:20: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:21: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:21: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:22: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-02 17:48:22: [Main]: Using game specified by --gameid on the command line
2022-02-02 17:48:23: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]

EDIT: For comparison here is the log when run on the previous release.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-02-02 18:01:11: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
        .__               __                   __   
  _____ |__| ____   _____/  |_  ____   _______/  |_ 
 /     \|  |/    \_/ __ \   __\/ __ \ /  ___/\   __\
|  Y Y  \  |   |  \  ___/|  | \  ___/ \___ \  |  |  
|__|_|  /__|___|  /\___  >__|  \___  >____  > |__|  
      \/        \/     \/          \/     \/        
2022-02-02 18:01:12: ACTION[Main]: World at [/config/.minetest/worlds/world]
2022-02-02 18:01:12: ACTION[Main]: Server for gameid="minetest" listening on 0.0.0.0:30000.
adrinux commented 2 years ago

I don't know if this is helpful but created another fresh server today, entered the container and ran minetestserver --trace

root@662ffdb2532f:/config# minetestserver --trace 
2022-02-04 11:57:34: [Main]: Enabling trace level debug output
2022-02-04 11:57:34: INFO[Main]: Using system-wide paths (NOT RUN_IN_PLACE)
2022-02-04 11:57:34: INFO[Main]: Detected share path: /usr/share/minetest
2022-02-04 11:57:34: INFO[Main]: Detected user path: /config/.minetest
2022-02-04 11:57:34: INFO[Main]: Detected cache path: /config/.cache/minetest
2022-02-04 11:57:34: INFO[Main]: minetest with SER_FMT_VER_HIGHEST_READ=28, BUILD_TYPE=Release
2022-02-04 11:57:34: INFO[Main]: RUN_IN_PLACE=0
2022-02-04 11:57:34: INFO[Main]: USE_CURL=1
2022-02-04 11:57:34: INFO[Main]: STATIC_SHAREDIR="/usr/share/minetest"
2022-02-04 11:57:34: VERBOSE[Main]: httpfetch_init: parallel_limit=8
2022-02-04 11:57:34: INFO[Main]: Message locale is now set to: C.UTF-8;C;C;C;C;C
2022-02-04 11:57:34: INFO[Main]: Searching worlds...
2022-02-04 11:57:34: INFO[Main]:   In /config/.minetest/worlds: world 
2022-02-04 11:57:34: INFO[Main]: 1 found.
2022-02-04 11:57:34: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-02-04 11:57:34: INFO[Main]: Using world gameid [minetest]
2022-02-04 11:57:34: VERBOSE[Main]: Using world path [/config/.minetest/worlds/world]
2022-02-04 11:57:34: VERBOSE[Main]: Using gameid [minetest]
2022-02-04 11:57:34: [Main]: UDPSocket(5)::UDPSocket(): ipv6 = false
2022-02-04 11:57:34: VERBOSE[ConnectionSend]: con(5/0)ConnectionSend thread started
2022-02-04 11:57:34: VERBOSE[ConnectionReceive]: con(5/0)ConnectionReceive thread started
2022-02-04 11:57:34: INFO[Main]: Server created for gameid "minetest"
2022-02-04 11:57:34: INFO[Main]: - world:  /config/.minetest/worlds/world
2022-02-04 11:57:34: INFO[Main]: - game:   /config/.minetest/games/minetest
2022-02-04 11:57:34: INFO[Main]: Initializing world at /config/.minetest/worlds/world
2022-02-04 11:57:34: INFO[Main]: ObjDefManager: added biome: name="default" index=0 uid=27
2022-02-04 11:57:34: INFO[Main]: EmergeManager: using 1 threads
2022-02-04 11:57:34: INFO[Main]: BanManager: loading from /config/.minetest/worlds/world/ipban.txt
2022-02-04 11:57:34: INFO[Main]: BanManager: failed loading from /config/.minetest/worlds/world/ipban.txt
2022-02-04 11:57:34: INFO[Main]: BanManager: creating /config/.minetest/worlds/world/ipban.txt
2022-02-04 11:57:34: VERBOSE[Main]: ServerMap::ServerMap(const string&, IGameDef*, EmergeManager*, MetricsBackend*)
2022-02-04 11:57:34: INFO[Main]: ServerMap: Metadata loaded from /config/.minetest/worlds/world
2022-02-04 11:57:34: INFO[Main]: Server: Initializing Lua
2022-02-04 11:57:34: INFO[Main]: SCRIPTAPI: Initialized game modules
2022-02-04 11:57:34: VERBOSE[Main]: Loading and running script from /usr/share/minetest/builtin/init.lua
Illegal instruction (core dumped)
bnounours commented 2 years ago

Hello, I have the same problem with verison 5.5.1 or 5.5.0

root@35bbee79688e:/# minetestserver --trace
2022-07-17 01:03:18: [Main]: Enabling trace level debug output
2022-07-17 01:03:18: INFO[Main]: Using system-wide paths (NOT RUN_IN_PLACE)
2022-07-17 01:03:18: INFO[Main]: Detected share path: /usr/share/minetest
2022-07-17 01:03:18: INFO[Main]: Detected user path: /config/.minetest
2022-07-17 01:03:18: INFO[Main]: Detected cache path: /config/.cache/minetest
2022-07-17 01:03:18: INFO[Main]: minetest with SER_FMT_VER_HIGHEST_READ=29, BUILD_TYPE=Release
2022-07-17 01:03:18: INFO[Main]: RUN_IN_PLACE=0
2022-07-17 01:03:18: INFO[Main]: USE_CURL=1
2022-07-17 01:03:18: INFO[Main]: STATIC_SHAREDIR="/usr/share/minetest"
2022-07-17 01:03:18: VERBOSE[Main]: httpfetch_init: parallel_limit=8
2022-07-17 01:03:18: INFO[Main]: Message locale is now set to: C.UTF-8;C;C;C;C;C
2022-07-17 01:03:18: INFO[Main]: Searching worlds...
2022-07-17 01:03:18: INFO[Main]:   In /config/.minetest/worlds: world 
2022-07-17 01:03:18: INFO[Main]: 1 found.
2022-07-17 01:03:18: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2022-07-17 01:03:18: INFO[Main]: Using world gameid [minetest]
2022-07-17 01:03:18: VERBOSE[Main]: Using world path [/config/.minetest/worlds/world]
2022-07-17 01:03:18: VERBOSE[Main]: Using gameid [minetest]
2022-07-17 01:03:18: [Main]: UDPSocket(5)::UDPSocket(): ipv6 = false
2022-07-17 01:03:18: VERBOSE[ConnectionSend]: con(5/0)ConnectionSend thread started
2022-07-17 01:03:18: VERBOSE[ConnectionReceive]: con(5/0)ConnectionReceive thread started
2022-07-17 01:03:18: INFO[Main]: Server created for gameid "minetest"
2022-07-17 01:03:18: INFO[Main]: - world:  /config/.minetest/worlds/world
2022-07-17 01:03:18: INFO[Main]: - game:   /config/.minetest/games/minetest
2022-07-17 01:03:18: INFO[Main]: Initializing world at /config/.minetest/worlds/world
2022-07-17 01:03:18: INFO[Main]: ObjDefManager: added biome: name="default" index=0 uid=15
2022-07-17 01:03:18: INFO[Main]: EmergeManager: using 1 threads
2022-07-17 01:03:18: INFO[Main]: BanManager: loading from /config/.minetest/worlds/world/ipban.txt
2022-07-17 01:03:18: VERBOSE[Main]: ServerMap::ServerMap(const string&, IGameDef*, EmergeManager*, MetricsBackend*)
2022-07-17 01:03:18: INFO[Main]: ServerMap: Metadata loaded from /config/.minetest/worlds/world
2022-07-17 01:03:18: INFO[Main]: Server: Initializing Lua
2022-07-17 01:03:18: INFO[Main]: SCRIPTAPI: Initialized game modules
2022-07-17 01:03:18: VERBOSE[Main]: Loading and running script from /usr/share/minetest/builtin/init.lua
Illegal instruction (core dumped)

When I try to open the file with luajit I get the same:

root@35bbee79688e:/# luajit /usr/share/minetest/builtin/init.lua
Illegal instruction (core dumped)

when trying luajit alone also ...

root@35bbee79688e:/# luajit
LuaJIT 2.1.0-beta3 -- Copyright (C) 2005-2021 Mike Pall. https://luajit.org/
JIT: ON SSE3 fold cse dce fwd dse narrow loop abc sink fuse
> help
Illegal instruction (core dumped)
artooro commented 1 year ago

Having a similar issue, except it the log does not show Illegal instruction it just constantly restarts with Automatically selecting world at [/config/.minetest/worlds/world]

But if I run luajit > help then I can get the same Illegal instruction error.

I wonder if there is some kind of CPU compatibility issue? I'm doing this on a Atom D525 CPU.

JasperKuiper commented 1 year ago

I'm trying this on a TrueNAS Scale server (up-to-date, using TrueCharts version of minetest 5.6.1_3.0.3), running on a AMD Athlon II X4 635, and having the same problem (looping with Automatically selecting world at [/config/.minetest/worlds/world]

Yes, I understand THIS is not the best place to file a report for MY particular issue, but I think there's some common ground here and my guess is @artooro is on to something....

Could it be something to do with SSE3??

> lscpu does NOT return a sse3 flag for my cpu, perhaps the same is true for the issues above?

adrinux commented 1 year ago

I'd forgotten about this. But still running 5.4.1 which works and need to upgrade to 5.6.1 for mods my kids want to use.

@JasperKuiper and @artooro You may be onto something - also running on an older/wimpy CPU, specifically an AMD Turion II Neo N40L (in a 10yr old HP Microserver). Ran lscpu, sse3 is not listed, just sse2 and sse4a.

adrinux commented 1 year ago

If I run luajit on the server itself it seems to work. BUT it core dumps when run from within the docker container.

I suppose linuxserver.io docker images are missing something?

adrinux commented 1 year ago

Confirmed that minetest-server 5.6.1 runs fine my CPU outside of docker.

I'm running on manjaro so installed minetest-server from the community repo. cd into the folder I usually mount in docker and ran minetest server with:

minetestserver --config main-config/minetest.conf --world worlds/world

Successfully logged into server and preexisting world still there (I did update mods and server db backend etc so everything was up to date.)

So a workaround at least.

mattsches commented 1 year ago

I've just tried running the latest release 5.6.1-LS106 and get the same error

Automatically selecting world at [/config/.minetest/worlds/world]

Trying to run it my older Synology NAS.

z-vap commented 1 year ago

Confirmed that minetest-server 5.6.1 runs fine my CPU outside of docker.

I'm running on manjaro so installed minetest-server from the community repo. cd into the folder I usually mount in docker and ran minetest server with:

minetestserver --config main-config/minetest.conf --world worlds/world

Successfully logged into server and preexisting world still there (I did update mods and server db backend etc so everything was up to date.)

So a workaround at least.

so the workaround is to change the CLI_ARGS to include this? Is that correct?

--config main-config/minetest.conf

edit: i've tried this and with no success. When running this manually I get 

minetestserver  --gameid devtest
2023-02-13 16:43:01: [Main]: Automatically selecting world at [/config/.minetest/worlds/world]
2023-02-13 16:43:01: [Main]: Using game specified by --gameid on the command line
Illegal instruction (core dumped)
adrinux commented 1 year ago

@z-vap No, you've misunderstood. The workaround is to not run Minetest in Docker. Run it directly on the System OS instead.

Those of us hitting this problem all appear to have older CPUs or modern but 'limited' CPUs that lack certain features, Minetest itself runs OK on these CPUs. But this Minetest Docker image needs to have those features to run.

z-vap commented 1 year ago

oh ok thanks. I take it there's no "at launch switches" that docker may support for older CPU's with this? I've been looking around but have not discovered any

adrinux commented 1 year ago

@z-vap

oh ok thanks. I take it there's no "at launch switches" that docker may support for older CPU's with this?

No, no launch switches. There is a minimal OS inside the container - in this case it's Alpine Linux and the issues appear to have started after the container image was updated to Alpine 3.15 in January 2022.

Making this work in Docker would probably require a custom image specifically for our hardware, I doubt this linuxserver.io image will ever work moving forward.

z-vap commented 1 year ago

Yeah my nas is definitely on older hardware. I do have more modern backup hardware, but I am thinking of migrating my whole setup to Proxmox. This may be my motivation.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity