Giter Club home page Giter Club logo

jammsen / docker-palworld-dedicated-server Goto Github PK

View Code? Open in Web Editor NEW
891.0 11.0 147.0 2.23 MB

Docker container to easily provision and manage Palworld Dedicated Server

Home Page: https://hub.docker.com/r/jammsen/palworld-dedicated-server

License: MIT License

Dockerfile 14.21% Shell 85.79%
dedicated-gameservers dedicated-server docker docker-compose gameserver gameservers palworld palworld-dedicated-server palworld-server palworld-server-docker

docker-palworld-dedicated-server's People

Contributors

aaomidi avatar actions-user avatar anzhizhang avatar caleb-devops avatar callum027 avatar dashboy1998 avatar eltociear avatar gchai avatar jammsen avatar jasonbristol avatar lexiv avatar m1xzg avatar mcs5234 avatar miguelrjim avatar mindflay3r avatar plarpoon avatar staleloafofbread avatar th3irdeye avatar thejcpalma avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-palworld-dedicated-server's Issues

[Feature Request] ENV Var for Tickrate

Have you read the Important information text above

  • Yes i did

Current behavior

In some cases for Experimenting, its useful to Set the tickrate lower. this can be be done in /Pal/Saved/Config/LinuxServer/Engine.ini
and paste at the bottom of the file following lines:

[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=60

Desired behavior

Please Add an ENV like NetServerMaxTickRate=30

Links to screenshots

Some Reddit post: https://www.reddit.com/r/Palworld/comments/19avqax/comment/kip5w5w/?utm_source=share&utm_medium=web2x&context=3

To Reproduce

Nothing to reproduce.

Software setup

  • OS: Ubuntu 22.04 LTS
  • Docker: 20.10.21

Hardware setup

  • vCPU: 6
  • RAM: 16GB
  • Disk: SSD 200GB

Additional context

This Container is Awesome!

Double slashes with $GAME_PATH

Have you read the Important information text above

  • Yes i did

Current behavior

The script tries to read /palworld//Pal/ since $GAME_PATH has a trailing slash.

Desired behavior

The script should read /palworld/Pal/

Links to screenshots

No response

To Reproduce

Run the servermanager.sh script

Software setup

  • Newest script with a689ffe35d12
  • Debian
  • Docker Compose

Hardware setup

  • Docker containerd virtualized hardware

Additional context

No response

Running this on a NAS without Steam

Have you read the Important information text above

  • Yes i did

Current behavior

First of all this is more of a question than an actual issue, sorry about that.

My goal is to run a Palworld dedicated server on my NAS, but in the code I'm seeing references to steam itself; am I supposed to install Steam as well?

Desired behavior

Run a server on my NAS

Links to screenshots

No response

To Reproduce

Software setup

  • OS: DSM 7.2-64570 Update 1
  • Docker: 20.10.23

Hardware setup

Additional context

No response

[Question] Accessing RCON via Portainer

I don't really know if this is the right place to ask but I am running your docker-compose image on Portainer. I cannot seem to easily access the RCON from there tho. Anyone else that had the same idea that knows how to do that?

It's not hard to access the inside of the container, I just don't know how to access the RCON itself from there, see below.
image

[Feature Request] - Automatically update game server files if server is idle

Have you read the Important information text above

  • Yes i did

Current behavior

need to manually restart container to download & apply updates from steam to game server

Desired behavior

check with XX interval if updated game server files are available from steam, then if new files are detected, check if server is 'idle' (either via RCON to get player count or by monitoring for a lack of UDP traffic), if server is idle, apply the update & restart game server. if server is not idle, RCON broadcast a message to let players know there is a pending update that needs to be applied.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. new feature request

Software setup

  • OS: centos
  • Docker: 25.0

Hardware setup

  • vCPU: 6
  • RAM: 16
  • Disk: 2tb

Additional context

No response

Fatal Error: Steamcmd needs to be online to update

Have you read the Important information text above

  • Yes i did

Current behavior

1.docker compose up -d
2.docker logs palworld-dedicated-server

error:

Doing a fresh install of the gameserver
time="2024-01-23T17:08:05Z" level=info msg="read crontab: cronlist"
tid(17) burning pthread_key_t == 0 so we never use it
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[ 0%] Checking for available updates...
[----] Verifying installation...
[ 0%] Downloading update...
[ 0%] Checking for available updates...
[----] !!! Fatal Error: Steamcmd needs to be online to update. Please confirm your network connection and try again.
src/tier0/threadtools.cpp (3706) : Assertion Failed: Illegal termination of worker thread 'Thread(0x0x570fbad0/0x0xf7732b'

i can not finish the install step

Desired behavior

none

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS: centos
  • Docker: 24.0.7

Hardware setup

  • vCPU: 4c
  • RAM: 14g
  • Disk: 1t

Additional context

No response

Root password

Have you read the Important information text above

  • Yes i did

Current behavior

I am running docker desktop. Within the container, exec, I run the following and permission is denied.

chown 1000:1000 /srv/palworld/game

Running this requests the root password

su root chown 1000:1000 /srv/palworld/game/

Desired behavior

Root by default.

Links to screenshots

No response

To Reproduce

su root chown 1000:1000 /srv/palworld/game/

Software setup

  • OS: Windows
  • Docker: 4.26.1

Hardware setup

  • vCPU: 16
  • RAM: 32
  • Disk: 1000

Additional context

No response

Errors while the docker deploys

Have you read the Important information text above

  • Yes i did

Current behavior

Running TrueNAS Scale.
Installed as a "Custom App".
Filled out all the environment variables.
When I look at /palworld its empty.

Log:
2024-01-24 11:06:30.789131-08:00>>> Starting the gameserver
2024-01-24 11:06:30.789185-08:00Checking if config exists
2024-01-24 11:06:30.789215-08:00No config found, generating one
2024-01-24 11:06:30.791439-08:00mkdir: cannot create directory '/palworld/Pal': Permission denied
2024-01-24 11:06:30.794619-08:00cp: cannot stat '/palworld/DefaultPalWorldSettings.ini': No such file or directory
2024-01-24 11:06:30.794975-08:00Setting rcon-enabled to true
2024-01-24 11:06:30.797733-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.798079-08:00Setting public ip to [redacted]
2024-01-24 11:06:30.800529-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.800700-08:00Setting public port to [redacted]
2024-01-24 11:06:30.803376-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.803654-08:00Setting server name to [redacted]
2024-01-24 11:06:30.805745-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.805908-08:00Setting server description to [redacted]
2024-01-24 11:06:30.807760-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.807982-08:00Setting server password to [redacted]
2024-01-24 11:06:30.810651-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.810974-08:00Setting server admin password to [redacted]
2024-01-24 11:06:30.812794-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.812991-08:00Setting max-players to [redacted]
2024-01-24 11:06:30.815658-08:00sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
2024-01-24 11:06:30.816546-08:00/servermanager.sh: line 81: ./PalServer.sh: No such file or directory

Desired behavior

for the server to start.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Create Custom App in TrueNAS Scale
  2. Add environmental vars settings
  3. Click Create App
  4. Check App logs

Software setup

  • OS: Linux
  • Docker: latest

Hardware setup

  • vCPU: Default
  • RAM: Default
  • Disk: Default

Additional context

No response

Properly auto-detect `PUBLIC_IP` when omitting from docker-compose.yml

Have you read the Important information text above

  • Yes i did

Current behavior

When omitting PUBLIC_IP from docker-compose.yml, it is not auto-detected and instead the PublicIp value in /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini set to 10.0.0.1.

For users, it is a bit hard to follow what the actual behavior of the container will be since the docs for PUBLIC_IP contradicts itself by stating auto-detect if not specified while also stating that the default value is 10.0.0.1. No auto-detection is taking place.

Desired behavior

Proper auto-detection of PUBLIC_IP

Two steps to this below.

Remove default value for PUBLIC_IP

Remove 10.0.0.1 as the default value from Dockerfile:

PUBLIC_IP=10.0.0.1 \

Reasons for this:

  1. 10.0.0.1 is slightly misleading as a default PUBLIC_IP since the 10.0.0.0/8 IP ranges are specially reserved for private networks. It's not a sensible default. In general, there really is no sensible default for PUBLIC_IP, which is why I'm opting for it to be removed as a default entirely.
  2. Omitting PUBLIC_IP will line up with the Setup for community server. instructions:

You can manually specify the global IP address of the network on which the server running. If not specified, it will be detected automatically. If it does not work well, try manual configuration.

  1. Instead of defining a default, the value can be dynamically populated when the container starts (see below).

Allow PUBLIC_IP to be detected and set dynamically

Add ability to set PUBLIC_IP environment variable to auto and make this the default value/behavior as currently noted in the README. This will automatically detect the network's public IP and set it in the game config. This is particularly useful for networks that do not have static IPs, as it removes the manual effort of reflecting changes to the public IP in docker-compose.yml. Even for networks with static IPs, it removes a manual step in the initial setup process.

General flow can go like this:

  1. Container is started and servermanager.sh script is run.
  2. startServer() is called and checks if PUBLIC_IP is either not set or set to the string auto.
  • If either of these expressions are true, execute command curl ifconfig.me to retrieve public IP address and replace PublicIp config value with this IP in /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini.
  • If something other than auto is defined for PUBLIC_IP, use that for the PublicIp config value.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Fresh clone or install of the repo, or remove cached images for the docker-compose project and set PublicIp to "" in game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini.
  2. Remove PUBLIC_IP env variable from docker-compose.yml
  3. docker-compose up -d wait for server to start (monitor with docker-compose logs -f)
  4. Run command cat /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (or wherever your config file is located), PublicIp will have been overridden to 10.0.0.1.

Software setup

  • OS: Slackware 15.0 x86_64 (post 15.0 -current)
    • i.e. Unraid 6.12.6
  • Docker: Docker version 20.10.24, build 297e128

Hardware setup

  • vCPU: 12
  • RAM: 104 GiB
  • Disk: 1 TB

Additional context

I'm happy to write a PR for this but I wanted to get your input beforehand.

[Feature Request] arm64 support?

Have you read the Important information text above

  • Yes i did

Current behavior

Currently the docker image only supports x86.

Desired behavior

For the image to support arm64 linux servers.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS: Ubuntu arm64 OCI
  • Docker:

Hardware setup

  • vCPU: 4
  • RAM: 24
  • Disk: 200

Additional context

Would it be posible to support arm64 servers by using certain emulators like box64 or skmething like that? I’ve seen some SteamCMD servers supported arm64 via box64 or something like that.

Add an Environment Option for bEnableNonLoginPenalty

Have you read the Important information text above

  • Yes i did

Current behavior

At the moment as discussed in a few open issues, the config file gets updated every time you start the server, so it loses custom configs for game settings you might want to change.

In this case I want to be able to disable bEnableNonLoginPenalty in PalWorldSettings.ini because as far as I understand, this is the option which causes all your Pals to be depressed, injured or whatever else when you first log in on the server every day. Which at the moment seems incredibly opressive, and annoying.

Desired behavior

An option to be able to set the setting inside the environmental options so it persists through restarts.

Links to screenshots

No response

To Reproduce

n/a

Software setup

n/a

Hardware setup

n/a

Additional context

No response

No content under palworld/game and cannot connect with server

Have you read the Important information text above

  • Yes i did

Current behavior

cannot see a game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini file, Or to be precise, there's nothing in the palworld/game folder.

and also I cannot connect with this server.

Desired behavior

The server is running and can be connected

Links to screenshots

No response

To Reproduce

I started the docker with the command below:

docker run --name palworld -p 8211 -e ALWAYS_UPDATE_ON_START=true -e MAX_PLAYERS=8 -e MULTITHREAD_ENABLED=true \
    -e COMMUNITY_SERVER=false -e PUBLIC_PORT=8211 -e PUBLIC_IP=43.139.150.139 -e SERVER_NAME=xworld \
    -e SERVER_DESCRIPTION="xx's pal world" -e SERVER_PASSWORD=xx233 -e ADMIN_PASSWORD=zaxs0130 \
    -v /home/ubuntu/palworld:/palworld \
    jammsen/palworld-dedicated-server

The log file has been uploaded to the attachment.
docker.log

Software setup

  • OS: Ubuntu22.04
  • Docker: Docker version 24.0.7, build afdd53b

Hardware setup

  • vCPU: 2 core
  • RAM: 8 GB
  • Disk: 80 GB

Additional context

No response

how to get back v0.1.2.0

Have you read the Important information text above

  • Yes i did

Current behavior

I tried all docker images tags, could not back to v0.1.2.0

Desired behavior

It's updated automatively. I want to back v0.1.2.0 is that possible?

Links to screenshots

No response

To Reproduce

none

Software setup

linux

Hardware setup

  • vCPU: 4h
  • RAM: 16g
  • Disk:220g

Additional context

No response

Docker shutdown signal not passed on

Have you read the Important information text above

  • Yes i did

Current behavior

When stopping the container, it seems to get killed after the stop_grace_period (default 10s).

Desired behavior

The stop signal should be passed onto the underlying service so that it shuts down cleanly within the grace period.

If the clean shutdown takes longer than 10 seconds, the image should set a higher grace period.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Stop the container
  2. See it always stops after 10 seconds

Software setup

  • OS: Ubuntu 22.04
  • Docker: 24.0.4
  • Docker compose: 2.19.1

Hardware setup

  • vCPU: 6
  • RAM: 16G
  • Disk: 280G SSD

Additional context

No response

Feature-Request: Please add a License

Have you read the Important information text above

  • Yes i did

Current behavior

Currently there is not license file in the repository.

Desired behavior

There should a license file so others know the licensing of the project.

Links to screenshots

No response

To Reproduce

View repository

Software setup

N/A

Hardware setup

N/A

Additional context

No response

[Feature Request] Scheduled Backups

Have you read the Important information text above

  • Yes i did

Current behavior

Server saves aren't backed up.

Desired behavior

The save files for the server should be backed up by some cron schedule, if desired, and controlled through environmental variables. Especially with the issues being reported about save files being lost.

Check out this Valheim server for a good example: https://github.com/lloesche/valheim-server-docker

BACKUPS=true
BACKUPS_CRON=0 * * * *
BACKUP_DIRECTORY=/something
etc...

Basically, we just set up a cronjob in the container to run the admin /Save command to do a forced save, then copy that save to the backup directory and date it.

Save folder:
/palworld/Pal/Saved/SaveGames/0/9D3D178236CA4DCD977E978D94FFD633/Players

Links to screenshots

No response

To Reproduce

NA

Software setup

NA

Hardware setup

NA

Additional context

No response

Please provide a unique docker tag:

Have you read the Important information text above

  • Yes i did

Current behavior

You tag everything latest which makes pulling new images harder than it needs to be

Desired behavior

Every time you push to dockerhub there should be a unique tag.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Docker Hub

Software setup

  • OS: Kubernetes

Hardware setup

A bunch of nodes

Additional context

https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375

In short, if you are re-using the latest tag, my system has no idea it should be pulling a newer image. If you do not want to look into versioning, just including the git short sha or something would make pulling the image easier.

Thanks.

Illegal instruction (core dumped)

Have you read the Important information text above

  • Yes i did

Current behavior

When I start the container it restarts every 20 seconds.

Desired behavior

DOCKER LOG:
Loading Steam API...OK

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: 7.45 (352381458 / 4729437191)
Update state (0x5) verifying install, progress: 19.68 (930940151 / 4729437191)
Update state (0x5) verifying install, progress: 31.92 (1509760814 / 4729437191)
Update state (0x5) verifying install, progress: 44.09 (2085244037 / 4729437191)
Update state (0x5) verifying install, progress: 56.47 (2670757946 / 4729437191)
Update state (0x5) verifying install, progress: 68.71 (3249510552 / 4729437191)
Update state (0x5) verifying install, progress: 81.02 (3831594787 / 4729437191)
Update state (0x5) verifying install, progress: 93.06 (4401165458 / 4729437191)
Success! App '2394010' fully installed.

Starting the gameserver
Checking if config exists
Setting rcon-enabled to true
Setting rcon-port to 25575
Setting public ip to ****
Setting public port to 49154
Setting server name to ****
Setting server description to Palworld-Dedicated-Server running in Docker by jammsen
Setting server password to *****
Setting server admin password to *****
Setting max-players to 32
Illegal instruction (core dumped)
Doing an update of the gameserver
tid(12) burning pthread_key_t == 0 so we never use it
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1705108307
-- type 'quit' to exit --

compose.yml:

version: '2.24.0'
services:
palworld-dedicated-server:
#build: .
container_name: palworld-dedicated-server
image: jammsen/palworld-dedicated-server:latest
restart: always
network_mode: bridge
ports:
- target: 49154 # gamerserver port inside of the container
published: 49154 # 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=true
- RCON_ENABLED=true
- RCON_PORT=25575
- PUBLIC_IP= ****
- PUBLIC_PORT=49154
- SERVER_NAME=****
- SERVER_DESCRIPTION=Palworld-Dedicated-Server running in Docker by jammsen
- SERVER_PASSWORD=****
- ADMIN_PASSWORD=****
- BACKUP_ENABLED=true
- BACKUP_CRON_EXPRESSION=0 * * * *
volumes:
- ./game:/palworld

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS: Debian 12
  • Docker: docker compose version 2.24.0

Hardware setup

  • vCPU:
  • RAM: 16go
  • Disk:256 go

Additional context

No response

[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.

Have you read the Important information text above

  • Yes i did

Current behavior

This problem occurs when I enter the game, and it prompts "no password has been entered." I deleted the password options directly in the docker-compose file, deleted the game folder, and reinitialized it. However, when entering the game, it still prompts "no password has been entered." How can I solve this issue?

Desired behavior

What should I do?

Links to screenshots

Snipaste_2024-01-21_11-05-22

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS: debian
  • Docker: Docker version 20.10.24+dfsg1, build 297e128

Hardware setup

  • vCPU: 5800H
  • RAM: 32G
  • Disk:2T

Additional context

No response

[Bug] Getting permission denied when the container is creating directories

Have you read the Important information text above

  • Yes i did

Current behavior

When the script reaches the starting game server step it is unable to create a directory and other files

palworld-dedicated-server  | >>> Starting the gameserver
palworld-dedicated-server  | Checking if config exists
palworld-dedicated-server  | No config found, generating one
palworld-dedicated-server  | mkdir: cannot create directory '/palworld/Pal': Permission denied

Desired behavior

I would like it to be able to create the folder and copy over the files

Links to screenshots

No response

To Reproduce

create a docker-compose.yml with this content

version: '3.9'
services:
  palworld-dedicated-server:
    # user: steam
    container_name: palworld-dedicated-server
    image: jammsen/palworld-dedicated-server:latest
    restart: always
    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:
      - TZ=Europe/Copenhagen # Change this for logging and backup, see "Environment-Variables"
      - ALWAYS_UPDATE_ON_START=true
      - MAX_PLAYERS=32
      - MULTITHREAD_ENABLED=true
      - COMMUNITY_SERVER=true
      - RCON_ENABLED=true
      - RCON_PORT=25575
      - PUBLIC_IP=10.0.0.5
      - PUBLIC_PORT=8211
      - SERVER_NAME=aaa
      - SERVER_DESCRIPTION=aaa
      - SERVER_PASSWORD=aaa
      - ADMIN_PASSWORD=Tamale-Enlarged7-Bush
      - BACKUP_ENABLED=true
      - BACKUP_CRON_EXPRESSION=0 * * * *
    volumes:
      - ./game:/palworld

and run sudo docker compose up

Software setup

  • OS: OS: Rocky Linux 8.8 (Green Obsidian) x86_64
  • Docker: Docker version 24.0.6, build ed223bc

Hardware setup

  • CPU: Intel i7-6700 (8) @ 4.000GHz
  • RAM: 25524MiB / 63985MiB
  • Disk: 110GB available

Additional context

If I run the following commands I can see that the user is correctly set to steam, but the folders have not been assigned ownership.

sudo docker exec -ti palworld-dedicated-server whoami
steam
sudo docker exec -ti palworld-dedicated-server ls -lah /palworld
total 12K
drwxr-xr-x. 2 root root 4.0K Jan 25 16:13 .
drwxr-xr-x. 1 root root 4.0K Jan 25 16:18 ..

ENV variables are ignored, and the game is starting with default config.

Have you read the Important information text above

  • Yes i did

Current behavior

The env variables in my docker compose is being ignored, and the game is set up using the default config.
I am running this on ubuntu server 22.04, with portainer.

How I know that it gets ignored is:

  1. I can enter the game without a password.
  2. When I type ingame /AdminPassword test, the game tells me that there's no admin password set.
  3. I can see in the ubuntu server htop that this is using all 4 cores, while I want to run this on 1 core.
  4. /dockerdata/palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini exists, but it is empty.

This is my docker compose:

 version: '3.9'
  services:
    palworld-dedicated-server:
      build: .
      container_name: palworld-dedicated-server
      image: jammsen/palworld-dedicated-server:latest
      restart: unless-stopped
      network_mode: bridge
      ports:
        - target: 8211
          published: 8211
          protocol: udp
          mode: host
      environment:
        - ALWAYS_UPDATE_ON_START=true
        - MAX_PLAYERS=16
        - MULTITHREAD_ENABLED=false
        - COMMUNITY_SERVER=false
        - PUBLIC_PORT=8211
        - SERVER_NAME="RER"
        - SERVER_DESCRIPTION="Palworld Dedicated Server"
        - SERVER_PASSWORD="112211"
        - ADMIN_PASSWORD="test"
      volumes:
        - /dockerdata/palworld:/palworld

Desired behavior

That the server is picking up the env variables.

Links to screenshots

.ini file is empty:
image

To Reproduce

Steps to reproduce the behavior:

  1. Go to portainer
  2. Click on create new stack from stacks
  3. Scroll down to click on deploy stack
  4. Enter the game, and see that your env variables are ignored

Software setup

  • OS: Ubuntu server 22.04
  • Docker: 25.0.0
  • Portainer: 19.3

Hardware setup

  • vCPU: i5-6500 4 core
  • RAM: 16gb
  • Disk: SSD 256gb

Additional context

No response

Server Logging

Have you read the Important information text above

  • Yes i did

Current behavior

Currently when I launch the server I see the last logs as

[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded

Are there further logs available from Palsworld (ex. logins, chat, server status) that could be made available?
I've tried adding the "-log" to the base command in servermanager.sh but doesn't seem to have made much of a difference. I may need to rebuild, or maybe the logs are getting piped elsewhere, or worse don't exist?

Desired behavior

Logs of server activity viewable with docker logs [container name here]

Links to screenshots

No response

To Reproduce

docker compose up
Connect to server and do stuff
View logs and see nothing has changed
or
docker logs [container name here]
and see nothing has been logged

Software setup

  • OS: 6.2.0-39-generic #40~22.04.1-Ubuntu
  • Docker: Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1

Hardware setup

  • vCPU: 6 cores 12 threads (Ryzen 5 3600)
  • RAM: 126GB RAM
  • Disk: 17TB/32TB available (4-disk ZFS Pool, 2 data 1 parity one hot swap)

Additional context

No response

Add queryport for community server

Have you read the Important information text above

  • Yes i did

Current behavior

The server is not visible in the list of community servers. The variable is set to COMMUNITY_SERVER=true

Desired behavior

Added the -queryport=XXX option to the command line, if the variable is configured and can customize the port

Links to screenshots

No response

To Reproduce

Start the server with the variable COMMUNITY_SERVER=true. The server is not visible

Software setup

  • OS: Debian 12
  • Docker: Docker 25.0.0

Hardware setup

  • vCPU: 8
  • RAM: 64G
  • Disk: 500G

Additional context

No response

/backupmanager.sh not found

Have you read the Important information text above

  • Yes i did

Current behavior

When the backupmanager cron job kicks off, it fails to find /backupmanager.sh
image

Desired behavior

backupmanager script can be found and backs up as expected.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

I have attempted to build the image myself as well as use your image.

[Bug] Server Crash

Have you read the Important information text above

  • Yes i did

Current behavior

About every 30 minutes 1 hour the server crashes

Desired behavior

docker version 2.24.0

Links to screenshots

Capture d'écran 2024-01-24 214625
Capture d'écran 2024-01-24 214258
Capture d'écran 2024-01-24 214207
Capture d'écran 2024-01-24 214128

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:Debian12
  • Docker:2.24.0

Hardware setup

  • vCPU:
  • RAM: 16
  • Disk:258go SSD

Additional context

No response

PalEggDefaultHatchingTime resets to 72 every time restarting container

Have you read the Important information text above

  • Yes i did

Current behavior

PalEggDefaultHatchingTime resets to 72 every time starting container.

Desired behavior

want to set PalEggDefaultHatchingTime in Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

Links to screenshots

image

To Reproduce

Steps to reproduce the behavior:

  1. Go to Pal/Saved/Config/LinuxServer/
  2. Open PalWorldSettings.ini
  3. Set PalEggDefaultHatchingTime to other value and restart container
  4. Open PalWorldSettings.ini again and you can see 72.000000 again

Software setup

  • OS: Linux version 5.4.0-169-generic (buildd@lcy02-amd64-102) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023
    (on Hyper-V)
  • Docker: Docker version 24.0.5, build 24.0.5-0ubuntu1~20.04.1

Hardware setup

  • vCPU: 8
  • RAM: 32GB
  • Disk: 128GB virtual disk

Additional context

I've tried 0.000000, 1.000000, 0, everything didn't work and PalEggDefaultHatchingTime resets to 72.000000 when initializing server.
setting DeathPenalty=None works. (DeathPenalty value persists when restarting container)

Feature-Request: Remove old Git-Hub Actions which are subject to be turned off

Have you read the Important information text above

  • Yes i did

Current behavior

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/login-action@v2, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
&
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Desired behavior

.

Links to screenshots

.

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

No response

`/home/steam/steamcmd/steamcmd.sh: line 39: 11 Segmentation fault $DEBUGGER "$STEAMEXE" "$@"`

Have you read the Important information text above

  • Yes i did

Current behavior

start failed: /home/steam/steamcmd/steamcmd.sh: line 39: 11 Segmentation fault $DEBUGGER "$STEAMEXE" "$@"

Desired behavior

successfully started server

Links to screenshots

image

To Reproduce

docker run

Software setup

  • OS: Linux OpenWrt 6.1.73 #0 SMP PREEMPT_DYNAMIC Thu Jan 18 09:40:58 2024 x86_64 GNU/Linux
  • Docker:
# docker version
Client:
 Version:           24.0.7
 API version:       1.43
 Go version:        go1.21.5
 Git commit:        afdd53b
 Built:             Thu Jan 18 09:40:58 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          24.0.7
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.21.5
  Git commit:       311b9ff
  Built:            Thu Jan 18 09:40:58 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.6
  GitCommit:
 runc:
  Version:          1.1.9
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Hardware setup

  • vCPU: Intel(R) Celeron(R) N5105 @ 2.00GHz : 4C4T
  • RAM: 4GB
  • Disk: SSD

Additional context

No response

/servermanager.sh: line 37: ./PalServer.sh: No such file or directory

At first I got the problem from the other issue but that seems to be fixed. Now I'm getting this error: /servermanager.sh: line 37: ./PalServer.sh: No such file or directory

Thanks for creating this Docker container though :)

Software setup

  • OS: Fedora Server

Edit:
Fixed by running this command: chown -R 1000:1000 game/
(thanks, @Lexiv)
Also, change the ports section to this so you can connect:
ports:
- "8211:8211/udp"

Can't log in

Have you read the Important information text above

  • Yes i did

Current behavior

mon container demarre correctement mais mon server n'apparait pas sur le jeu et e n'arrive pas a me connecter meme avec l'adresse IP publique IP_PUBLIC:PORT
I opened my ports on my router port 49154/UDP. Do I also need to open port 25575? If so, can I change the port? It's been done before and it wasn't working.

Desired behavior

Docker Compose version v2.24.0-birthday.10

Links to screenshots

docker logs
Capture d'écran 2024-01-24 041553

compose.yml:
Capture d'écran 2024-01-24 041852

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS: Debian 12
  • Docker: 2.24.0

Hardware setup

  • vCPU:
  • RAM: 16
  • Disk:258

Additional context

No response

Bug-Fix: Variables set cant be unset

Have you read the Important information text above

  • Yes i did

Current behavior

When i set server password and want to make it public again, the old config isnt changed and i see nothing the console of the change.

Desired behavior

Working as intended

Links to screenshots

.

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

No response

Container crashes with error: Illegal instruction (core dumped)

Have you read the Important information text above

  • Yes i did

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

  • OS: OpenMediaVault 6.3.2-2
  • Docker: 20.10.23

Hardware setup

  • CPU: AMD Phenom(tm) II X4 965 Processor
  • RAM: 23.39 GiB
  • Disk: 358,12 GiB free

Additional context

No response

[BUG] Fails to detect existing configuration and overwrites it with default template

Have you read the Important information text above

  • Yes i did

Current behavior

Despite having existing config files mounted, it fails to detect them and overwrites them with the template, every single time.
This has started happening today (likely related to #5), after the docker image was updated.

Desired behavior

Existing mounted config files should be respected.

Links to screenshots

image

To Reproduce

  1. Launch the docker container to generate config files, then shut it down
  2. Change config files as needed
  3. Launch the docker container again
  4. Config is overwritten by template

Software setup

  • OS: Ubuntu 22.04.3 LTS
  • Docker: Docker 24.0.5, Docker Compose 1.29.2

Hardware setup

  • CPU: Intel i7-10710U (6C/12T)
  • RAM: 32gb
  • Disk: 2 TB nvme

Additional context

No response

Permission denied

Have you read the Important information text above

  • Yes i did

Current behavior

>>> Starting the gameserver
Checking if config exists
No config found, generating one
mkdir: cannot create directory '/palworld/Pal': Permission denied
cp: cannot stat '/palworld/DefaultPalWorldSettings.ini': No such file or directory
Setting rcon-enabled to true
Setting public ip to 10.0.0.5
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Setting public port to 8211
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Setting server name to jammsen-docker-generated-###RANDOM###
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Found standard template, using random numbers in server name
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Server name is now jammsen-docker-generated-3640
Setting server description to Palworld-Dedicated-Server running in Docker by jammsen
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Setting server password to
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Setting server admin password to admin8888
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
Setting max-players to 32
sed: can't read /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini: No such file or directory
/servermanager.sh: line 81: ./PalServer.sh: No such file or directory
>>> Doing a fresh install of the gameserver
time="2024-01-25T03:09:16Z" level=info msg="read crontab: cronlist"
tid(17) burning pthread_key_t == 0 so we never use it
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'

My region is China, may there be some download failure during the process of linking to Steam due to network issues?

Desired behavior

Expected to be able to access the server, but I am unable to access it

Links to screenshots

No response

To Reproduce

Sorry,I don't know.

Software setup

  • OS:Centos 7
  • Docker:

Hardware setup

  • vCPU: R7 7735
  • RAM: 8G
  • Disk:50G

Additional context

No response

Question about methods for configuration

Have you read the Important information text above

  • Yes i did

Current behavior

Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.

Desired behavior

Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.

Links to screenshots

No response

To Reproduce

Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.

Software setup

Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.

Hardware setup

Why, after modifying the PalWorldSettings.ini configuration and restarting the Docker container, does the PalWorldSettings.ini configuration revert to the default settings? I don't want to use variable methods for configuration.

Additional context

No response

[Feature Request] Update Docker Hub Readme on CI-push

Have you read the Important information text above

  • Yes i did

Current behavior

I have to copy paste manually every change i do in the readme.md here to publish it to docker-hub

Desired behavior

A Github Actions CI-solution updates the readme on docker-hub from here.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

No response

[Bug] Cannot update patch

Have you read the Important information text above

  • Yes i did

Current behavior

Since palworld has new patch https://steamdb.info/app/2394010/config/
I docker compose down the server and docker pull the latest image
but always show Error! App '2394010' state is 0x606 after update job.

i also git pull the latest repo

Desired behavior

want to update successfully

Links to screenshots

圖片

To Reproduce

Steps to reproduce the behavior:

docker compose down
docker pull jammsen/palworld-dedicated-server:latest
git pull
docker compose up

Software setup

  • OS: Ubuntu 20.04.4 LTS
  • Docker: 24.0.7

Hardware setup

  • vCPU: 32
  • RAM: 64G
  • Disk: 1TB

Additional context

No response

RCON is possible, maybe add the ports to expose it?

Have you read the Important information text above

  • Yes i did

Current behavior

I can enable the RCON in the server if i expose the port, maybe it could be added to the docker-compose.yml?

Desired behavior

Add it either to the description of the repo or the docker-compose file it could be usefull for other people.

Links to screenshots

image

To Reproduce

  • Add this to the docker compose file:
    ports:
      - "25575:25575/udp"
      - "25575:25575/tcp"
  • enable RCONEnabled=True and setup a port in RCONPort=25575 in the /game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

You wil need a way to connect to the RCON of the game. i use: https://github.com/gorcon/rcon-cli

Software setup

  • OS: Ubuntu 22.04 LTS
  • Docker: Docker version 25.0.0, build e758fe5

Hardware setup

  • vCPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
  • RAM: 16GB
  • Disk: 500GB

Additional context

No response

Unable to start container process: exec: "/servermanager.sh": permission denied - Day 1 Release Bug-Fixes - Community-Thread

Have you read the Important information text above

  • Yes i did

Current behavior

Container will not start with the provided Docker Compose. Trying to deploy the container via Portainer. I created an app-template using the provided Docker Compose and I receive the below error when trying to deploy the image:

Deployment error
failed to deploy a stack: Container palworld-dedicated-server Creating Container palworld-dedicated-server Created Container palworld-dedicated-server Starting Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/servermanager.sh": permission denied: unknown

This could be a lack of understanding on my part. Thanks for any help you can provide.

Desired behavior

Container should start

Links to screenshots

image

To Reproduce

Steps to reproduce the behavior:

  1. Create App-Template
  2. Paste Docker Compose template and modify env variables
  3. Deploy new container based on template
  4. See error

Software setup

  • OS: Proxmox
  • Docker:

Hardware setup

  • vCPU: 3950x
  • RAM: 64gb
  • Disk: 2tb

Additional context

No response

GHCR docker container?

Have you read the Important information text above

  • Yes i did

Current behavior

Container is only shared on docker hub.

Desired behavior

GitHub Container Registry is also a place to get the containers from

Links to screenshots

No response

To Reproduce

N/A

Software setup

N/A

Hardware setup

N/A

Additional context

GHCR has a lot more permissive rate limiting.

PalWorld.sh not found

Have you read the Important information text above

  • Yes i did

Current behavior

server crash when someone try to join

Desired behavior

people can join the server and play

Links to screenshots

palworld-dedicated-server | Connecting anonymously to Steam Public...OK
palworld-dedicated-server | Waiting for client config...OK
palworld-dedicated-server | Waiting for user info...OK
palworld-dedicated-server | Update state (0x11) preallocating, progress: 0.00 (0 / 4729437191)
palworld-dedicated-server | Error! App '2394010' state is 0x202 after update job.
palworld-dedicated-server | >>> Starting the gameserver
palworld-dedicated-server | Checking for config
palworld-dedicated-server | /servermanager.sh: line 48: ./PalServer.sh: No such file or directory
palworld-dedicated-server | >>> Doing a fresh install of the gameserver
palworld-dedicated-server | tid(11) burning pthread_key_t == 0 so we never use it
palworld-dedicated-server | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
palworld-dedicated-server | Logging directory: '/home/steam/Steam/logs'
palworld-dedicated-server | [ 0%] Checking for available updates...
palworld-dedicated-server | [----] Verifying installation...
palworld-dedicated-server | Steam Console Client (c) Valve Corporation - version 1705108307
palworld-dedicated-server | -- type 'quit' to exit --
palworld-dedicated-server | Loading Steam API...OK
palworld-dedicated-server |
palworld-dedicated-server | Connecting anonymously to Steam Public...OK
palworld-dedicated-server | Waiting for client config...OK
palworld-dedicated-server | Waiting for user info...OK
palworld-dedicated-server | Update state (0x11) preallocating, progress: 0.00 (0 / 4729437191)
palworld-dedicated-server | Error! App '2394010' state is 0x202 after update job.
palworld-dedicated-server | >>> Starting the gameserver
palworld-dedicated-server | Checking for config
palworld-dedicated-server | /servermanager.sh: line 48: ./PalServer.sh: No such file or directory

To Reproduce

clone the repo
create a game folder with chmod 777 on it
edit config with correct ip and port
start docker compose
stop docker compose
edit game/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
start docker compose
try to connect with a windows client

Software setup

  • OS: Linux
  • Docker: Docker version 24.0.7, build afdd53b

Hardware setup

  • vCPU: x86 family
  • RAM: 4go
  • Disk: 256 ssd

Additional context

I didn't go inside the container to create the game directory.
I didn't install steam steamcmd and run everything. Maybe it should be add to the documentation if needed

Server issue with passwords

Have you read the Important information text above

  • Yes i did

Current behavior

After entering a password for the server, the game fails to connect with the following error. The game never prompts for a password. Not sure where the disconnect is.

Desired behavior

The server appears to be handling password incorrectly somehow.

Links to screenshots

image

To Reproduce

Steps to reproduce the behavior:

  1. Setup the docker container with the following env variables.
environment:
      - ALWAYS_UPDATE_ON_START=true
      - MAX_PLAYERS=10
      - MULTITHREAD_ENABLED=true
      - COMMUNITY_SERVER=false
      - PUBLIC_IP=[Enter your public IP here]
      - PUBLIC_PORT=8211
      - SERVER_NAME=Server Name
      - SERVER_DESCRIPTION=A default server description
      - SERVER_PASSWORD=Password123
      - ADMIN_PASSWORD=NotAPassword123*
  1. Load game and connect to server
    image

  2. See error mentioned in earlier screenshot

Software setup

  • OS: Windows 11 v22621.3007
  • Docker: 4.26.1 (131620)

Hardware setup

Processor: 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz
Installed RAM: 32.0 GB (31.8 GB usable)
System type: 64-bit operating system, x64-based processor

Additional context

No response

Refactor: Docker-Compose in Readme not as files

Have you read the Important information text above

  • Yes i did

Current behavior

Docker-Compose should be in the README not as file, its dublicate content to care of.

Desired behavior

Docker-Compose should be in the README not as file, its dublicate content to care of.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

No response

[Bug] Fix logical error on #20

Have you read the Important information text above

  • Yes i did

Current behavior

We cant change the Dockerfile RCON_PORT anyway, but mount it outside via Docker-Compose to where we want it. So this settings in the Docker-related files and scripts are not usefull.

Desired behavior

See Current

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Software setup

  • OS:
  • Docker:

Hardware setup

  • vCPU:
  • RAM:
  • Disk:

Additional context

No response

Using with XBMC version of the game

Have you read the Important information text above

  • Yes i did

Current behavior

Sorry this is probably not the appropriate way to ask - but can this be used with the XBMC version of the game or only as long as it has the same version? Could a specific version be enforced to keep it alive in case XBMC version is behind?

Desired behavior

as above

Links to screenshots

No response

To Reproduce

./

Software setup

./

Hardware setup

./

Additional context

please delete if that is the wrong place please, don'T want it to be a burden for you guys

COMMUNITY_SERVER variable default

Have you read the Important information text above

  • Yes i did

Current behavior

The README states that the default value for COMMUNITY_SERVER is set to false. However, in the Dockerfile and docker-compose files, it is set to true. Therefore, if you start the container without this environment variable set, it will default to true given the logic in servermanager.sh file. One must explicitly set COMMUNITY_SERVER=false if you do not wish to add it to the list of community servers. I think this requires clarification in the README or a code change to ensure it is set to false by default.

Desired behavior

When starting the container without the COMMUNITY_SERVER environment variable set, it should not append the EpicApp=PalServer argument, unless explicitly set to true

Links to screenshots

No response

To Reproduce

$ docker run --rm -it --entrypoint /bin/sh docker.io/jammsen/palworld-dedicated-server
$ env | grep COMMUNITY
COMMUNITY_SERVER=true

Software setup

Hardware setup

Additional context

No response

[Help] Cant run the RCON commands at all

Have you read the Important information text above

  • Yes i did

Current behavior

With the README.md dockerfile, when i try to run sudo docker-compose run --rm rcon info i got the following log:

cli: execute: auth: rcon: dial tcp 10.0.0.5:25575: i/o timeout
ERROR: 1

I dont know much about the rcon, but shouldnt the ip(10.0.0.5) be somehow a link to the palworld container?

Desired behavior

When running the RCON info command, receive the rcon info feedback

Links to screenshots

image

To Reproduce

Steps to reproduce the behavior:

  1. Use the docker-compose.yml with rcon example
  2. do the docker-compose up -d
  3. execute the command: $ docker-compose run --rm rcon info
  4. See the log

Software setup

  • OS: Ubuntu Server 22.04
  • Docker: 25.0.1

Hardware setup

  • vCPU: 4
  • RAM: 16
  • Disk: 60

I'm currently using the aws ec2 t3a.xlarge

Additional context

No response

[Bug] No such image: moby/buildkit:buildx-stable-1

Have you read the Important information text above

  • Yes i did

Current behavior

image
[steam@VM-4-15-centos ~]$ vi docker-compose.yml
[steam@VM-4-15-centos ~]$ docker-compose up -d
[+] Running 0/1
? palworld Pulling 2.5s
[+] Building 2.6s (1/1) FINISHED docker-container:default
=> ERROR [palworld internal] booting buildkit 2.6s
=> => pulling image moby/buildkit:buildx-stable-1 2.6s
=> => creating container buildx_buildkit_default 0.0s

[palworld internal] booting buildkit:


Error response from daemon: No such image: moby/buildkit:buildx-stable-1
[steam@VM-4-15-centos ~]$

Desired behavior

这个镜像依赖的相关东西我无法下载

Links to screenshots

No response

To Reproduce

[steam@VM-4-15-centos ~]$ vi docker-compose.yml
[steam@VM-4-15-centos ~]$ docker-compose up -d
[+] Running 0/1
? palworld Pulling 2.5s
[+] Building 2.6s (1/1) FINISHED docker-container:default
=> ERROR [palworld internal] booting buildkit 2.6s
=> => pulling image moby/buildkit:buildx-stable-1 2.6s
=> => creating container buildx_buildkit_default 0.0s

[palworld internal] booting buildkit:


Error response from daemon: No such image: moby/buildkit:buildx-stable-1
[steam@VM-4-15-centos ~]$

Software setup

。。

Hardware setup

..

Additional context

No response

[Feature Request] - Daily/scheduled game server restarts if no players connected

Have you read the Important information text above

  • Yes i did

Current behavior

container must be manually restarted (or a system cron job created to restart it) and if players are connected, this risks save file corruption.

Desired behavior

container uses a daily (or other interval) script against (possible options)

  • RCON to see if players are connected, if no players are connected, it restarts the game server or if players are connected then either skips the scheduled reboot or does a broadcast message to the server that the reboot is pending in XX minutes
  • if RCON isn't a good option, can the incoming UDP datagrams be monitored and if no UDP traffic in YY interval, declare server is 'idle' and restart game server?

why this is needed: early access games typically have memory leaks that over time lead to poor performance or file corruption. less risk of corrupting saves if restarted with no players connected.

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

  1. new feature request

Software setup

  • OS: centos
  • Docker: 25.0

Hardware setup

  • vCPU: 6
  • RAM: 16
  • Disk: 2tb

Additional context

No response

steamcmd: cannot execute binary file: Exec format error

Have you read the Important information text above

  • Yes i did

Current behavior

Steamcmd: cannot execute binary file: Exec format error and then No such file or directory
UGREEN NAS is used

Desired behavior

normal operation

Links to screenshots

Clip_2024-01-21_17-49-27

To Reproduce

Directly run 100% reproduction

Software setup

  • OS: Linux UGREEN-E563 5.10.120 #0 SMP Fri Dec 29 03:07:23 2023 x86_64 GNU/Linux
  • Docker: Docker version 20.10.16, build aa7e414

Hardware setup

  • vCPU: Intel(R) Pentium(R) Silver N6005 @ 2.00GHz
  • RAM: 8+16
  • Disk:

/dev/dm-0 465.5G 4.9G 460.7G 1% /mnt/dm-0
/dev/dm-1 12.7T 3.4T 9.4T 27% /mnt/dm-1
/dev/dm-2 931.1G 80.3G 850.7G 9% /mnt/dm-2
/dev/dm-3 931.1G 429.1G 501.9G 46% /mnt/dm-3
/dev/dm-4 7.3T 3.8T 3.4T 53% /mnt/dm-4

Additional context

[
{
"Id": "624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355",
"Created": "2024-01-21T09:39:02.179784799Z",
"Path": "/servermanager.sh",
"Args": [],
"State": {
"Status": "exited",
"Running": false,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 0,
"ExitCode": 127,
"Error": "",
"StartedAt": "2024-01-21T09:39:03.646234758Z",
"FinishedAt": "2024-01-21T09:39:03.65898544Z"
},
"Image": "sha256:eeec45f90325dd9fba8b142f5340e4582186b885e2617399bd2569a7fed517ee",
"ResolvConfPath": "/mnt/dm-2/.ugreen_nas/6/containers/624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355/resolv.conf",
"HostnamePath": "/mnt/dm-2/.ugreen_nas/6/containers/624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355/hostname",
"HostsPath": "/mnt/dm-2/.ugreen_nas/6/containers/624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355/hosts",
"LogPath": "/mnt/dm-2/.ugreen_nas/6/containers/624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355/624dcc0310290cdb6adbd5b5f76ad84ca24388ba1f0339b9aca6b6537ddc5355-json.log",
"Name": "/palworld-dedicated-server",
"RestartCount": 0,
"Driver": "overlay2",
"Platform": "linux",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "default",
"PortBindings": {
"8211/udp": [
{
"HostIp": "0.0.0.0",
"HostPort": "8211"
},
{
"HostIp": "::",
"HostPort": "8211"
}
]
},
"RestartPolicy": {
"Name": "",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": [
"AUDIT_WRITE",
"CHOWN",
"DAC_OVERRIDE",
"FOWNER",
"FSETID",
"KILL",
"MKNOD",
"NET_BIND_SERVICE",
"NET_RAW",
"SETUID",
"SETGID"
],
"CapDrop": [],
"CgroupnsMode": "private",
"Dns": null,
"DnsOptions": null,
"DnsSearch": null,
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "private",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "runc",
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": null,
"DeviceCgroupRules": null,
"DeviceRequests": null,
"KernelMemory": 0,
"KernelMemoryTCP": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": null,
"OomKillDisable": null,
"PidsLimit": null,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0,
"Mounts": [
{
"Type": "bind",
"Source": "/mnt/media_rw/19f2a024-6119-438d-ba72-5975dbdd3a1a/.ugreen_nas/248447/Docker/GAME-SEVER/palworld-server/game",
"Target": "/palworld",
"Consistency": "default"
}
],
"MaskedPaths": [
"/proc/asound",
"/proc/acpi",
"/proc/kcore",
"/proc/keys",
"/proc/latency_stats",
"/proc/timer_list",
"/proc/timer_stats",
"/proc/sched_debug",
"/proc/scsi",
"/sys/firmware"
],
"ReadonlyPaths": [
"/proc/bus",
"/proc/fs",
"/proc/irq",
"/proc/sys",
"/proc/sysrq-trigger"
]
},
"GraphDriver": {
"Data": {
"LowerDir": "/mnt/dm-2/.ugreen_nas/6/overlay2/914cb8284fa0100e188c30cb45123891e88179e119b0029482a90c608f433ad9-init/diff:/mnt/dm-2/.ugreen_nas/6/overlay2/663ee0298cc8b6179c0cf9c4e01eb68c8b12fdccac561e1d6c5dc799566559ab/diff:/mnt/dm-2/.ugreen_nas/6/overlay2/b7bd5fb6e1082f0b43199a86bfc13cd3d81f88351c9c70b9a7aee68917f69684/diff:/mnt/dm-2/.ugreen_nas/6/overlay2/b89d2a2ee56e04305b71f8162171f5cbf1f9bad656548e318e0ec031172b0312/diff:/mnt/dm-2/.ugreen_nas/6/overlay2/bfd9c68024d53ef754ebd477d8a0f47dc9a285531f6355503943c0b2315cdeaa/diff",
"MergedDir": "/mnt/dm-2/.ugreen_nas/6/overlay2/914cb8284fa0100e188c30cb45123891e88179e119b0029482a90c608f433ad9/merged",
"UpperDir": "/mnt/dm-2/.ugreen_nas/6/overlay2/914cb8284fa0100e188c30cb45123891e88179e119b0029482a90c608f433ad9/diff",
"WorkDir": "/mnt/dm-2/.ugreen_nas/6/overlay2/914cb8284fa0100e188c30cb45123891e88179e119b0029482a90c608f433ad9/work"
},
"Name": "overlay2"
},
"Mounts": [
{
"Type": "bind",
"Source": "/mnt/media_rw/19f2a024-6119-438d-ba72-5975dbdd3a1a/.ugreen_nas/248447/Docker/GAME-SEVER/palworld-server/game",
"Destination": "/palworld",
"Mode": "",
"RW": true,
"Propagation": "rprivate"
}
],
"Config": {
"Hostname": "61c48d8ffd0b",
"Domainname": "",
"User": "steam",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"8211/udp": {}
},
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"USER=steam",
"HOMEDIR=/home/steam",
"STEAMCMDDIR=/home/steam/steamcmd",
"TIMEZONE=Europe/Berlin",
"DEBIAN_FRONTEND=noninteractive",
"PUID=1000",
"PGID=1000",
"ALWAYS_UPDATE_ON_START=false",
"MAX_PLAYERS=32",
"MULTITHREAD_ENABLED=true",
"COMMUNITY_SERVER=false",
"PUBLIC_IP=0.0.0.0",
"PUBLIC_PORT=8211",
"SERVER_NAME=jammsen-docker-generated-###RANDOM###",
"SERVER_DESCRIPTION=Palworld-Dedicated-Server running in Docker by jammsen",
"SERVER_PASSWORD=serverPasswordHere",
"ADMIN_PASSWORD=adminPasswordHere"
],
"Cmd": [
"/servermanager.sh"
],
"Healthcheck": {},
"Image": "jammsen/palworld-dedicated-server:latest",
"Volumes": {
"/palworld": {}
},
"WorkingDir": "/home/steam/steamcmd",
"Entrypoint": null,
"OnBuild": null,
"Labels": {
"maintainer": "[email protected]",
"org.opencontainers.image.authors": "Sebastian Schmidt",
"org.opencontainers.image.source": "https://github.com/jammsen/docker-palworld-dedicated-server"
}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "2b81136387e8229356c4ab0efd7719b1eda59e02260f80826da703ba5ab6b96a",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {},
"SandboxKey": "/var/run/docker/netns/2b81136387e8",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "5304ff48af8f0348b7e736c5195e9fda4a7743e6b7014ea3c65b83c4bedb147c",
"EndpointID": "",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "",
"DriverOpts": null
}
}
}
}
]

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.