Closed CruiseTian closed 2 months ago
Same issue here
If you delete your steamapps
folder inside the palworld
directory and restart the server, do you still have the same issue?
Please make sure you backup your folder before doing so.
I executed docker-compose up -d
in a brand new folder (without the palworld
folder in it) and still have this problem.
I can't seem to reproduce, if you use the thijsvanloef/palworld-server-docker:v0.28.2
image does it work?
I'm sorry, but the v0.28.2
version doesn't work for me either.
Also, this seems to be a steamcmd issue, because when I tried to install the Palworld game using a steamcmd
image, it also showed this error.
I checked out the steamcmd repo and noticed that two weeks ago the latest docker image of steamcmd was upgraded from Debian 11 to Debian 12. After that, I pulled the Debian 11 image provided by steamcmd using docker pull cm2network/steamcmd:steam-bullseye
. And I successfully installed, and launched the Palworld server.
Could you please provide an image based on the steamcmd:steam-bullseye
version to fix this issue?
@burkewm If needed, you can temporarily avoid this issue by using the image I just built based on steamcmd:steam-bullseye
using docker pull cruisetian/palworld-server-docker:v0.29-bullseye
, it works fine for me.
Sadly I am not planning on supporting older versions of debian
Describe the bug
After updating to the latest version (v0.29) of Docker, the server fails to start. The stderr.txt file in the Steam/log folder shows the following error:
src/tier0/threadtools.cpp (3830) : Assertion Failed: Failed to create thread (error 0x1)
, The complete content in stderr.txt is as follows:To Reproduce
Steps to reproduce the behavior:
docker exec palworld-server backup
docker-compose up -d
Expected behavior
Server restart successfully.
Actual behavior
Server can not start and steamcmd get
Assertion Failed
errorScreenshots
container status![image](https://github.com/thijsvanloef/palworld-server-docker/assets/50127078/59c8202c-ad82-40b2-8273-f8666d7a497c)
container log![image](https://github.com/thijsvanloef/palworld-server-docker/assets/50127078/b9717a0a-2b2b-4866-a045-d4a45a81bf86)
stderr log![image](https://github.com/thijsvanloef/palworld-server-docker/assets/50127078/43e4e51a-4760-454f-b55b-4d7dddba9870)
OS information
Hardware information
docker-compose.yml contents
Container/Host Logs
Additional context
My previously used docker image version is v0.24.0, and it works perfect.