search

jammsen / docker-palworld-dedicated-server

Docker container to easily provision and manage Palworld Dedicated Server
https://hub.docker.com/r/jammsen/palworld-dedicated-server
MIT License
911 stars 158 forks source link

Container crashes with error: Illegal instruction (core dumped) #25

Closed lsahnicne closed 9 months ago

lsahnicne commented 9 months ago

Have you read the Important information text above

Current behavior

Server crashes with the following text in logs: Illegal instruction (core dumped)

Desired behavior

Server runs properly

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Pull the image with

docker pull jammsen/palworld-dedicated-server

  1. Creater docker-compose file with the following contents:

version: '3.9' services: palworld-dedicated-server: build: . container_name: palworldserver image: jammsen/palworld-dedicated-server:latest restart: unless-stopped network_mode: bridge ports:

  • target: 8211 # gamerserver port inside of the container published: 8211 # gamerserver port on your host protocol: udp mode: host
  • target: 25575 # rcon port inside of the container published: 25575 # rcon port on your host protocol: tcp mode: host environment:
  • ALWAYS_UPDATE_ON_START=true
  • MAX_PLAYERS=32
  • MULTITHREAD_ENABLED=true
  • COMMUNITY_SERVER=false
  • RCON_ENABLED=false
  • RCON_PORT=25575
  • PUBLIC_IP=1.2.3.4
  • PUBLIC_PORT=8211
  • SERVER_NAME=servername
  • SERVER_DESCRIPTION=server
  • SERVER_PASSWORD=xxxxxxxxxxx
  • ADMIN_PASSWORD=xxxxxxxx volumes:

    - ./game:/palworld

  • /srv/palworld:/palworld

    rcon: image: outdead/rcon:latest entrypoint: ['/rcon', '-a', '10.0.0.5:25575', '-p', 'adminPasswordHere'] profiles: ['rcon']

  1. Up the dockerfile
  2. Wait for downloads to complete
  3. Container keeps restarting with the following messages in logs:

Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Update state (0x5) verifying install, progress: 0.00 (0 / 4729437191) Update state (0x5) verifying install, progress: 4.59 (217113154 / 4729437191) Update state (0x5) verifying install, progress: 14.85 (702350583 / 4729437191) Update state (0x5) verifying install, progress: 25.43 (1202528046 / 4729437191) Update state (0x5) verifying install, progress: 34.03 (1609375534 / 4729437191) Update state (0x5) verifying install, progress: 44.90 (2123466873 / 4729437191) Update state (0x5) verifying install, progress: 55.95 (2646093743 / 4729437191) Update state (0x5) verifying install, progress: 66.20 (3130910237 / 4729437191) Update state (0x5) verifying install, progress: 76.51 (3618301150 / 4729437191) Update state (0x5) verifying install, progress: 85.61 (4048669143 / 4729437191) Update state (0x5) verifying install, progress: 96.78 (4577164587 / 4729437191) Success! App '2394010' fully installed. >>> Starting the gameserver Checking if config exists Setting rcon-enabled to false Setting rcon-port to 25575 Setting public ip to 1.2.3.4 Setting public port to 8211 Setting server name to servername Setting server description to server Setting server password to xxxxxxxxxxx Setting server admin password to xxxxxxxx Setting max-players to 32 Illegal instruction (core dumped)

Software setup

Hardware setup

Additional context

No response

jammsen commented 9 months ago

Hey @lsahnicne was this version of the container working before? Is this a fresh install? What are the permission on the "game" directory?

jbettencourt10 commented 9 months ago

Just out of curiosity, how much ram are you running with? I believe I was having this error because my server has 8 GB of ram (some being used by other services, so actually less), and Palworld at minimum requires 8gb of ram to my knowledge.

lsahnicne commented 9 months ago

Hey @lsahnicne was this version of the container working before? Is this a fresh install? What are the permission on the "game" directory?

The error appeared the first time I tried to run this Docker image. Do you mean fresh install of image or Docker itself? For the latter - no, it was a while since I last tinkered with it, but it still runs a couple of containers and I used to host Conan Exiles server through Docker image on it no problem. As for the directory, as you can see in the composite file I posted above, I named it simply "srv\palworld", because "game" is very non-specific, and gave it rwxrwxrwx permiasions. Does it NEED to be named "game"?

Just out of curiosity, how much ram are you running with? I believe I was having this error because my server has 8 GB of ram (some being used by other services, so actually less), and Palworld at minimum requires 8gb of ram to my knowledge.

As you can see in the "Hardware Setup" section of the issue, my server has 23.39 GiB of RAM and usually around 20 of those are free.

P.s. issue closed and re-opened and comment edited due to Github's mobile UI being prone to accidental button presses and not asking for confirmatio when closing the issue.

jammsen commented 9 months ago

Hey @lsahnicne "Does it NEED to be named "game"?" No not really but i have to use a known term, for you to understand what im talking about and the "game" directory should be known if you read my readme. Fresh install of Docker no, i meant fresh install of the latest docker-compose file and the latest docker-image.

ComputersWithTimo commented 9 months ago

@lsahnicne make sure the permissions are set up correctly. As a test, u could chmod -R 777 /srv/palworld.

I had a similar issue when I was moving Hosts on Podman (because of memory restrictions). The server did start, but immediately crashed once a player connected because it wasn't able to write to its folder.

P.s. u can run a small server on just 4GB of RAM, but it will get laggy quickly.

Edit: I just saw your message with the permissions above. Must have slipped by! Make sure the files in the folder are also writable

lsahnicne commented 9 months ago

Issue identified thanks to the duplicate #41 - I have the exact same CPU and it appears to simply be too old to run this game's server :(