search

jammsen / docker-sons-of-the-forest-dedicated-server

Docker container to easily provision and manage Sons of the Forest Dedicated Server with Wine
https://hub.docker.com/r/jammsen/sons-of-the-forest-dedicated-server
134 stars 19 forks source link

Stuck in loop installing - steambootstrapper #28

Closed iamdaaan closed 8 months ago

iamdaaan commented 9 months ago

Current behavior

The docker container cannot seem to find a file called steambootstrapper_english.txt? It doesn't seem to be able to even install the game server

To Reproduce

Steps to reproduce the behavior:

  1. Copy the Docker run command
  2. View container logs

Software setup

Hardware setup

Docker Desktop Logs: 2023-10-24 11:53:51 >>> Doing a fresh install of the gameserver 2023-10-24 11:53:55 Redirecting stderr to '/root/Steam/logs/stderr.txt' 2023-10-24 11:53:55 Looks like steam didn't shutdown cleanly, scheduling immediate update check 2023-10-24 11:53:55 ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt". 2023-10-24 11:53:55 [ 0%] Checking for available update... 2023-10-24 11:53:55 [ 0%] Download Complete. 2023-10-24 11:53:55 [----] Applying update... 2023-10-24 11:53:55 [----] Extracting package... 2023-10-24 11:53:55 [----] Extracting package... 2023-10-24 11:53:55 [----] Extracting package... 2023-10-24 11:53:55 [----] Extracting package... 2023-10-24 11:53:55 [----] Installing update... 2023-10-24 11:53:55 [----] Cleaning up... 2023-10-24 11:53:55 [----] Failed to remove temporary unzip folder, continuing anyway 2023-10-24 11:53:55 [----] Update complete, launching... Just restarts the same loop after this...

gitzec commented 9 months ago

Idk, maybe you need to switch to Linux containers on Docker Desktop on Windows?

Also, if you plan to run the server on your gaming rig... Why not just launch the server (which is a Windows application) right on your PC? You won't need Docker or Wine at all this way. Just use a simple cmd/bat or PowerShell script to launch it.

iamdaaan commented 9 months ago

Im already using WSL containers instead of Hyper-V, and I'm planning on migrating to a server PC at some point so was wanting to get Docker containers ready to move across

gitzec commented 9 months ago

In this situation I would recommend to create an Ubuntu server VM, install Docker on it and start with docker-compose.

I used Docker Desktop years ago and had many issues with it. That's why these Windows/Linux containers switch came into my mind... All issues just vanished for me after switching to Docker in a real Linux VM inside Hyper-V.

jammsen commented 8 months ago

Hey have you tried the Windows equavilent of Linux's "chmod 777 directory" on your directories that you try to volumen-mount?

jammsen commented 8 months ago

@iamdaaan is the problem solved? Can this issue be closed?

jammsen commented 8 months ago

Closed because of inactivity

PontyJohnty commented 7 months ago

Sorry appreciate this is closed, but i had this problem on Docker Desktop via Windows 11 (WSL) and also on Synology NAS. Using Portainer on both.

I was able to resolve both issues by binding to a volume as follows with docker compose.

    volumes:
     - sons-of-the-forest-1:/sonsoftheforest
     - sons-of-the-forest-1:/steamcmd
     - sons-of-the-forest-1:/winedata

volumes:
  sons-of-the-forest-1:

To edit the dedicated server config file is easy enough in windows, you just need to find the volume, which for me was:

\wsl.localhost\docker-desktop-data\data\docker\volumes\sons-of-the-forest-ds_sons-of-the-forest-1

Synology NAS was more tricky and i ended up installing filebrowser in docker with "srv" set to the volume container manager was on and find it through there.

I hope this helps anyone in this position.

jammsen commented 7 months ago

Sorry appreciate this is closed

If someone steals a closed thread i might get a little angry or 🙄 but not for posting solutions, your fine! So thanks for helping!

Synology NAS was more tricky and i ended up installing filebrowser in docker with "srv" set to the volume container manager was on and find it through there.

Please be aware, that at least to my knowledge, that most Synology or QNAP NAS'es dont even have more then 4GB of RAM. But you need at least 6GB of RAM for this dedicated server alone to my extensive testing at that time. See here #7

PontyJohnty commented 7 months ago

Hey no problem; thank you for taking the time to containerise this!

Can also confirm, 6GB used on my synology. I have 20GB in total, so plenty of headroom.