Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] ich777 - Gameserver Dockers

Featured Replies

I'm new to Unraid and relatively new to Dockers, but not new to hosting gameservers using VMs. I was ambitious and got several game server dockers from the App store, including Icarus, Soulmask, and Rust. I spun them up with networking and pinged them across the wire, ports configured in UDM-Pro, started the containers... I'm hearing there's an issue with running multiple steamcmd docker containers but there is a setting that I need to configure to make this run correctly, is that right? Current symptom with Rust is that it seems to keep resetting after inflating files, and although I do not see the container restart, the runtime never goes past 7 or 8 seconds.

  • Replies 12.6k
  • Views 2.2m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Just thought I'd share my experience setting up a Valheim server with this docker app from @ich777(thank you!)   You don't need to worry about Steam authentication for Valheim, the default a

  • Dockers Available:   SteamCMD DedicatedServers: CounterStrike: Source CounterStrike 2 TeamFortress 2 ArmA3 - requested by @MrSage Deathmatch Classic

  • This will hopefully shed some light on the underside working bits of building a cluster of servers for ARK:SurvivalEvolved.   With the inspiration (read thievery) from @growlith I present th

Posted Images

  • Author
2 hours ago, sirrand said:

I spun them up with networking and pinged them across the wire, ports configured in UDM-Pro

You can‘t ping them most of the times since they wont respond to a ping or port checker because these are not web servers and usually don‘t have their own IP address.

 

2 hours ago, sirrand said:

I'm hearing there's an issue with running multiple steamcmd docker containers

Where did you hear that, you can run all of my containers at once if you really want to, of course if you configure them correctly in terms of ports so that they don‘t overlap.

 

2 hours ago, sirrand said:

Current symptom with Rust is that it seems to keep resetting after inflating files

Can you explain that a bit more in detail please? On what hardware are you running the containers? Did you change anything in the template? Did you use your Steam Credentials in the template (don‘t do that!)? Did you yet change any setting files for the container? What paths have you set up in the template? Do you have container logs or any log?

On 6/10/2024 at 1:46 AM, ich777 said:

Maybe but unfortunately I don't accept any more requests for Docker container because I have about 180 applications in the CA App.

 

Sorry...

Ahh I see I wonder if I can make one is there any pointers you can suggest?

  • Author
11 minutes ago, Landermark said:

Ahh I see I wonder if I can make one is there any pointers you can suggest?

Maybe:

 

On 6/13/2024 at 12:11 AM, ich777 said:

Fine... :D
If someone is willing to donate the game I create a container. ;)

Appreciate you! I was also trying to use your template to create a Soulmask container also but couldn't figure it out... I'm slowly beginning to understand how to create them but glad you made this so i can learn from it too! Thanks again! 

On 6/6/2024 at 5:00 AM, ich777 said:

@tito07 & @Wadzwigidy the container should now work again, please update the container itself and try to start it with BepInEx enabled.

Please note that the first container start after the update a bit longer (about 2 Minutes) at the message "---Start Server---" but the following restarts should work normal.

 

You don't have to set any environment variables or anything, the container does everything on it's own.

AWESOME!! Thank you!! Please, Have a cup of coffee on me good sir!

Hello!

 

I have a problem with KillingFloor 2.

Says in log "ERROR! Failed to install app '232130' (No subscription)"

 

What can I do?

 

This is the LOG:

---Prepare Server---
---Start Server---
---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1718305764
-- type 'quit' to exit --
Loading Steam API...OK
Logging in user '???' to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1718305764
-- type 'quit' to exit --
Loading Steam API...OK
Logging in user '???' to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
ERROR! Failed to install app '232130' (No subscription)

 

Template:

docker run
  -d
  --name='KillingFloor2'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="KillingFloor2"
  -e 'GAME_ID'='232130'
  -e 'GAME_PARAMS'='kf-bioticslab'
  -e 'VALIDATE'='VALIDATE'
  -e 'USERNAME'='???'
  -e 'PASSWRD'='???'
  -e 'UID'='99'
  -e 'GID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/killingfloor2.png'
  -p '8888:7777/udp'
  -p '27016:27015/udp'
  -p '8083:8080/tcp'
  -p '20560:20560/udp'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache_doc/appdata/killingfloor2':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:killingfloor2'
da8cb987d55dae0917672de49ff9589231cf116eb6f10997ee0afd5350d01771

The command finished successfully!

 

 

  • Author
8 minutes ago, gevsan said:
Logging in user '???' to Steam Public...OK

The answer is simple, please don‘t fill in Steam credentials.

 

Steam credentials are only required if they are not hidden away at the Show more settings… section and marked with the red asterisk!

2 minutes ago, ich777 said:

The answer is simple, please don‘t fill in Steam credentials.

 

Steam credentials are only required if they are not hidden away at the Show more settings… section and marked with the red asterisk!

Thanks! :D

How or where can I set a map rotation for CS2?

  • Author
8 hours ago, AceBurn90 said:

How or where can I set a map rotation for CS2?

This is a game specific question and has nothing to do with the container itself.

However if you search something like: "cs2 dedicated server set up map rotation" you will find how to do it eg: here or here

  • Author

@sirrand did you solve your issue with Soulmask already? It is most likely the case that you where using /mnt/cache/... in the template where your appdata share was maybe configured to be moved off of the cache to the array and that causes usually such a behavior.

 

BTW, did you figured out the issue from last week with RUST on your machine too?

So there was and is going to be updates soon which will support Xbox for Palworld via the Steam server (https://tech.palworldgame.com/getting-started/for-xbox-dedicated-server)

 

I was trying to get this updated as currently its in testing and am stuck when i try and run 

 

/serverdata/steamcmd/steamcmd.sh +login anonymous +app_update 2394010 -beta insiderprogram validate +quit

 

I get the following 

Redirecting stderr to '/root/Steam/logs/stderr.txt'
Logging directory: '/root/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1718751852
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
ERROR! Failed to install app '2394010' (Missing file permissions)

Some redit posts have found that the server needs to be re-installed fully using the beta branch but as this docker does it all automatically on boot (Thanks btw :) ) how would one go about getting this sorted? or how can one bypass this error above?

Edited by brent3000
added link

  • Author
19 minutes ago, brent3000 said:

I was trying to get this updated as currently its in testing and am stuck when i try and run 

Did you do that manually, if yes please don't do that since you could basically destroy your installation by doing it manually.

 

The container can do that for you (also mentioned in the template) :
grafik.png.9bcc95a2aa0490189cf3e055eacc60f4.png

then you have to set validation to true (you have click on "Show more settings..." to get to that variable) :

grafik.png.64f80aab05fc59a161be4b4f7bf5377a.png

 

After the container restarts the command will be executed. I would also recommend that you unset validation after the update was successful.

 

24 minutes ago, brent3000 said:

Some redit posts have found that the server needs to be re-installed fully using the beta branch but as this docker does it all automatically on boot

No you don't have to do that, if you set validation and the parameter in GAME_ID from above it will validate the files for the beta branch and therefore delete the unnecessary files and install the necessary files.

47 minutes ago, ich777 said:

The container can do that for you (also mentioned in the template) :

Its funny me playing around I came across the script the docker runs (https://github.com/ich777/docker-steamcmd-server/blob/master/scripts/start-server.sh) and noticed that the GAMEID seems to be the spot where that command would fit in when the docker runs, some testing it seems to be loading now just working on some config changes.

 

I wish I read all the orange font not just the first portion where the '.' is :) silly me. Would have saved me needing to dig into the code for it :D 

 

Handy to know on the validate section also will remove that as it seems to be online for now.

 

 

51 minutes ago, ich777 said:

Did you do that manually, if yes please don't do that since you could basically destroy your installation by doing it manually.

I did have to do some resets and full reinstalls of the docker which lead me to the fact that is not the way it should be done :) Tried to over diagnose it but got there in the end. 

 

Also appreciate the reply, I shall read all the text next time for these dockers :) I at least read the notes where the config and default passwords are all located, so there is that bonus :) 

Hello ich777,

I'm using your awesome Valheim docker. It is possible my problem is not related to your docker, but currently I'm facing back up issues.
Specifically whenever I stop & start my array or when your Valheim docker has an update and I update it through the Unraid WebUI. How does the automatic back up work, really? I changed the back up settings to 45 minute interval and allowed for 64 back ups total. Unfortunately the docker (as well as the internal valheim autobackup) only sporadically creates back ups.

Me and my friends meet up weekly on Tuesday to play, but all the .tar archives are never from the date when we actually played. The last Tuesdays were 28.05, 04.06, 11.06 and 18.06, but all my back up archives are dated to all other days BUT these Tuesdays. Why does this happen? Typically this wouldn't be too big a problem, but in our case it is, because I had to restart my array yesterday which stopped all dockers. When restarting the valheim docker, the world was replaced with an empty one and my last back up was dated on 17.06, just right before we started playing, losing all of our progress. How can this be? There should've been back ups from 18.06, 19.06 and 20.06 atleast. Hopefully you can make some sense of this, thank you

Edit: Looking at the dates more closely, I found a pattern: back ups work fine from Saturday through Monday but at Tuesday the back ups suddenly stop, only to start again at Saturday, effectively always missing our Tuesday dates.

Edited by Fortesque

  • Author
13 hours ago, Fortesque said:

When restarting the valheim docker, the world was replaced with an empty one and my last back up was dated on 17.06, just right before we started playing, losing all of our progress. How can this be?

Please go to you Shares tab and post a screenshot from your appdata share settings and also post a screenshot from the valheim docker template.

2 hours ago, ich777 said:

Please go to you Shares tab and post a screenshot from your appdata share settings and also post a screenshot from the valheim docker template.

Will do.

ShareSettings.png

ValheimDocker.png

  • Author
12 minutes ago, Fortesque said:

Will do.

Your issue is simple, in the share settings you have configured that appdata is moved to the Array (which is a bad idea in my opinion since appdata should stay on the cache) and in the template you have configured that the path to your gamefiles is /mnt/cache/appdata/… (which is the default) so to speak the container will write always to /mnt/cache/… and after the mover is invoked everything that is not in use will be moved over to the Array and therefore if you start/restart the container won‘t find the data in the correct spot.

 

You have two options:

  1. In the share settings set the cache to the primary storage and male sure that the move moves the files from the array (this is what I would recommend
  2. Set the path to /mnt/user/appdata/… in the template (I‘m strongly angainst this since this introduces more latency and maybe higher cpu usage because it must go through the FUSE filesystem).
4 minutes ago, ich777 said:

Your issue is simple, in the share settings you have configured that appdata is moved to the Array (which is a bad idea in my opinion since appdata should stay on the cache) and in the template you have configured that the path to your gamefiles is /mnt/cache/appdata/… (which is the default) so to speak the container will write always to /mnt/cache/… and after the mover is invoked everything that is not in use will be moved over to the Array and therefore if you start/restart the container won‘t find the data in the correct spot.

 

You have two options:

  1. In the share settings set the cache to the primary storage and male sure that the move moves the files from the array (this is what I would recommend
  2. Set the path to /mnt/user/appdata/… in the template (I‘m strongly angainst this since this introduces more latency and maybe higher cpu usage because it must go through the FUSE filesystem).

Well, that makes a lot of sense. I thought Unraid (and its containers) would just know that the mover was invoked and correctly look for data in the right place. That should help with the new world generation every time the docker is restarted AFTER mover was invoked.

But what about no back ups after Monday (I had the Mover scheduled on Monday)? Is my theory correct, that this is due to the moving of the files, since the back up only looks for data in cache/appdata? After moving, on Tuesday there would be no data in cache/appdata, but with the docker still running, we would still be able to play. Docker restart would then regenerate a new world and back ups of all days past Tuesday wouldn't exist, right?

  • Author
3 minutes ago, Fortesque said:

I thought Unraid (and its containers) would just know that the mover was invoked and correctly look for data in the right place.

If you set the path in the template to /mnt/user/… it would actually look for the data on both the array and cache but as said I don‘t recommend that.

 

4 minutes ago, Fortesque said:

But what about no back ups after Monday (I had the Mover scheduled on Monday)? Is my theory correct, that this is due to the moving of the files, since the back up only looks for data in cache/appdata? After moving, on Tuesday there would be no data in cache/appdata, but with the docker still running, we would still be able to play. Docker restart would then regenerate a new world and back ups of all days past Tuesday wouldn't exist, right?

Sorry but I‘m not here to speculate, there are too many variables involved.

 

I can only tell you if you change it like I recommended above, this won‘t happen any more and everything will work as expected (I still recommend changing the share setting so that data is moved from the array to the cache or simply set mover to none but that is also a bad idea since you know have files on the cache an array in your appdata share which isn‘t ideal anyway in my opinion).

10 minutes ago, ich777 said:

If you set the path in the template to /mnt/user/… it would actually look for the data on both the array and cache but as said I don‘t recommend that.

 

Sorry but I‘m not here to speculate, there are too many variables involved.

 

I can only tell you if you change it like I recommended above, this won‘t happen any more and everything will work as expected (I still recommend changing the share setting so that data is moved from the array to the cache or simply set mover to none but that is also a bad idea since you know have files on the cache an array in your appdata share which isn‘t ideal anyway in my opinion).

Ok, I'm confident your changes will help. Thank you for everything so far, as well as all your free support, you are a gentleman and a scholar.

  • Author
2 minutes ago, Fortesque said:

Ok, I'm confident your changes will help. Thank you for everything so far, as well as all your free support, you are a gentleman and a scholar.

Just for confirmation:

  1. Change the appdata share so that the mover is moving files from the array to the cache
  2. Invoke the Mover

(maybe stop all containers before invoking the mover and wait for it to finish)

Hello

I am having a small issue with the Soulmask Docker, might just be me as I didn't see it reported since the "Fine, I'll do Soulmask post 😁".

 

I have set everything up as per usual, port forwarding, ran through the variables etc and the game appears perfectly in the in-game browser, it just appears that it's using version 0.1.0 and will not allow me to connect as it's too old.

Is there a way I can set it to use the very latest?

 

I have tried restarting the container and verifying my files but no luck so far. I don't see any other newer branches on SteamDB 3017300 either. (only seems to show public)

 

Has anyone got this to work on latest version? (Seems to be 0.1.5 in the server list at time of this post)

Edited by Spoods

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.