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

Hey @ich777,

just a quick question.

Is in 7DaysToDie version 21 available and how can I check what Version is installed?

I already restartet the server but dont know if the old or new version is currently running.

 

UPDATE:

Nevermind... just got the update notification. Several minutes ago there was no update available.

 

UPDATE 2:

Hmm... was a Docker-update and not a game-update.

 

UPDATE 3:

My bad... In the Docker settings you (me) have to set the game id to "294420 -beta latest_experimental" for it to work.

Edited by AceBurn90

  • Replies 12.5k
  • 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

9 minutes ago, ich777 said:

I would strongly recommend that you read the descriptions from the variables in the template:

grafik.thumb.png.3bcb620e7321e63827bc40ea092fcfec.png

 

You can also join @Spectral Force's Discord server, he helps me out with 7DtD support: Click

 

Sigh.... sorry for being stupid, I thought I looked through everything, but that's pretty obvious, thanks for the reply and the discord link

  • Author
2 minutes ago, AceBurn90 said:

Hey @ich777,

just a quick question.

Is in 7DaysToDie version 21 available and how can I check what Version is installed?

I already restartet the server but dont know if the old or new version is currently running.

This is a good question that I can't answer but you always can take a look here: Click

 

You can also join @Spectral Force's Discord server, he helps me out with 7DtD support: Click

5 minutes ago, AceBurn90 said:

Hey @ich777,

just a quick question.

Is in 7DaysToDie version 21 available and how can I check what Version is installed?

I already restartet the server but dont know if the old or new version is currently running.

 

Alpha 21 isn't released as a Stable version yet so nothing will update (unless you have already messed with allowing beta builds to install) until it goes from experimental to stable (tentatively targeted in mid July). So should still be A20.7B1. If you did want to update to A21 now for the client side you have to go into steam and under the game properties then under Betas section and select "latest_experimental - Unstable build". Then based on ich777's reply to my question above adjust the game id of the container to match the build.

  • Author
18 minutes ago, Xenoc said:

Then based on ich777's reply to my question above adjust the game id of the container to match the build.

Exactly, but if you are switching between versions you also have to set Force Update to 'true' (without quotes) since SteamCMD needs to validate the files first <- this is also true when downgrading to stable (AFAIK downgrading is not recommended).

 

Please set Force Update to 'false' (without quotes) or nothing after the container updated the game.

2 hours ago, ich777 said:

I then think this is related to the game and not to the container itself but I also have to say that you are the second one who is reporting this, I think the other user also had a AMD CPU.

Where is the game data located? On a SSD or HDD?

 

I would strongly recommend that you report that to the game developers since my container is not much different than if you run it on bare metal.

Thanks for the reply! 

It is on my SSD cache. I will report this issue to them and see if they can help. Thank you for your response!

I'm trying to test out 7DaysToDie version 21, but on a clear install the docker after starting gets stuck with the CPU at 100%.

 

This is the output log: 

 

Mono path[0] = '/serverdata/serverfiles/7DaysToDieServer_Data/Managed'
Mono config path = '/serverdata/serverfiles/7DaysToDieServer_Data/MonoBleedingEdge/etc'
Preloaded 'libEOSSDK-Linux-Shipping.so'
Preloaded 'libMagick.so'
Preloaded 'lib_burst_generated.so'
Preloaded 'libgetrss.so'
Preloaded 'libsteam_api.so'
Preloaded 'steamclient.so'
Unable to preload the following plugins:
	libMouseLib.so
Loading player data from /serverdata/serverfiles/7DaysToDieServer_Data/data.unity3d
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps/7 Days To Die - Dedicated
Unable to load player prefs
Desktop is 0 x 0 @ 0 Hz

 

This is the console log:

Success! App '294420' fully installed.
---Prepare Server---
---Moving SaveGameFolder location---
---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

 

Any ideas?

 

46 minutes ago, IppoKun said:

I'm trying to test out 7DaysToDie version 21, but on a clear install the docker after starting gets stuck with the CPU at 100%.

 

This is the output log: 

 

Mono path[0] = '/serverdata/serverfiles/7DaysToDieServer_Data/Managed'
Mono config path = '/serverdata/serverfiles/7DaysToDieServer_Data/MonoBleedingEdge/etc'
Preloaded 'libEOSSDK-Linux-Shipping.so'
Preloaded 'libMagick.so'
Preloaded 'lib_burst_generated.so'
Preloaded 'libgetrss.so'
Preloaded 'libsteam_api.so'
Preloaded 'steamclient.so'
Unable to preload the following plugins:
	libMouseLib.so
Loading player data from /serverdata/serverfiles/7DaysToDieServer_Data/data.unity3d
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps/7 Days To Die - Dedicated
Unable to load player prefs
Desktop is 0 x 0 @ 0 Hz

 

This is the console log:

Success! App '294420' fully installed.
---Prepare Server---
---Moving SaveGameFolder location---
---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

 

Any ideas?

 

Same thing happens for me with a fresh pull from app store

  • Author
4 hours ago, IppoKun said:

Any ideas?

4 hours ago, Putz.Jimmy said:

Same thing happens for me with a fresh pull from app store

Does this also happen with the stable version from the game, so to speak when leaving everything at default in the template?

12 minutes ago, ich777 said:

Does this also happen with the stable version from the game, so to speak when leaving everything at default in the template?

Nope it starts just fine as vanilla

same here for me, this only happen if im running the 294420 -beta latest_experimental build

  • Author
7 minutes ago, Putz.Jimmy said:

Nope it starts just fine as vanilla

I‘ll have to contact @Spectral Force on this, maybe something changed or a new dependencies was introduced with the update or the current build from the game is broken…?

 

I really don‘t know since I‘m not that familiar with 7DtD.

  • Author

@Putz.Jimmy & @ws76 & @LapCheong I have no way of checking currently if it is working or not but can you try to do a complete fresh install? It seems to run on my server:

grafik.png.ac9c9821e9b3f319d02a73161443940e.png

 

However as said above I have currently no way of trying if it really is working and I got those lines in the log:
 

...

---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

 

 

As said, this is a completely fresh installed container.

10 minutes ago, ich777 said:

@Putz.Jimmy & @ws76 & @LapCheong I have no way of checking currently if it is working or not but can you try to do a complete fresh install? It seems to run on my server:

grafik.png.ac9c9821e9b3f319d02a73161443940e.png

 

However as said above I have currently no way of trying if it really is working and I got those lines in the log:
 

...

---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

 

 

As said, this is a completely fresh installed container.

 

I also get the same log output as you. Looking a bit further into it, I see the game is not creating save files or building worlds. If you modify the "serverconfig.xml" and change the "GameName" value to something different, this would normally trigger a new world to be built when the docker is restarted. As of right now, it's not building anything.

Experimental for a reason eh? Lol

@ich777 Uninstalled, deleted folder and did a clean install. 

Success! App '294420' fully installed.
---Prepare Server---
---Moving SaveGameFolder location---
---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

Connection to server failed and I can't access the web admin panel.

9 minutes ago, ws76 said:

@ich777 Uninstalled, deleted folder and did a clean install. 

Connection to server failed and I can't access the web admin panel.

Yup exactly the same outcome as you guys but still fail to join. Typically when the server is up and running, there should be output in the log located 7DaysToDie_Data/output_log.txt. Where it generate the world and if you try to join during that process you will get a "Server is currently initializing, please try in a few minutes".

10 minutes ago, LapCheong said:

Yup exactly the same outcome as you guys but still fail to join. Typically when the server is up and running, there should be output in the log located 7DaysToDie_Data/output_log.txt. Where it generate the world and if you try to join during that process you will get a "Server is currently initializing, please try in a few minutes".

Here is the output_log.txt I get.

Mono path[0] = '/serverdata/serverfiles/7DaysToDieServer_Data/Managed'
Mono config path = '/serverdata/serverfiles/7DaysToDieServer_Data/MonoBleedingEdge/etc'
Preloaded 'libEOSSDK-Linux-Shipping.so'
Preloaded 'libMagick.so'
Preloaded 'lib_burst_generated.so'
Preloaded 'libgetrss.so'
Preloaded 'libsteam_api.so'
Preloaded 'steamclient.so'
Unable to preload the following plugins:
	libMouseLib.so
Loading player data from /serverdata/serverfiles/7DaysToDieServer_Data/data.unity3d
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps
PlayerPrefs - Creating folder: /serverdata/.config/unity3d/The Fun Pimps/7 Days To Die - Dedicated
Unable to load player prefs
Desktop is 0 x 0 @ 0 Hz

The libMouseLib.so appears to be in the correct folder. 

  • Author
24 minutes ago, ws76 said:

Here is the output_log.txt I get.

38 minutes ago, LapCheong said:

Yup exactly the same outcome as you guys but still fail to join.

54 minutes ago, Nightingale said:

I also get the same log output as you.

From what I can tell the server expects to have a desktop environment which it doesn't have.

 

Did someone report that already to the developers?

Is there maybe a new startup option that needs to be used?

Is the server running in general on bare metal on Linux?

 

Please keep in mind that it has a reason why it's named "experimental" ;)

Same issues with 7dtd. I tried moving over an A21 save and loading it, but same results. Will try a bare metal linux install and see what happens...

for successufully install alpha 21 on 7 day you need to add headless= on boot.config  7DaysToDieServer_Data folder
And remove auto update with let validate blank on app and its launch successful but when update all files replace with new please FIX =D

  • Author
18 minutes ago, moreni said:

please FIX

What should I fix? This is a thing the game devs should fix in the first place.

 

You have to understand that this would be the same as if the devs would push an update without validation enabled the file would be always overwritten.

 

So to speak they should add headless= to the boot.cfg by default.

I know it is super fresh but the Update 8 for Satisfactory seems to just boot loop. Doesn't seem to dump any errors I can find. This is a fresh install of the docker and server files. If you were not aware of this I just wanted to make sure you were and see if you had any tips.

 

My assumption is it has something to do with the Unreal Engine update but I don't know this for sure.

  • Author
8 minutes ago, Pocketpac said:

I know it is super fresh but the Update 8 for Satisfactory seems to just boot loop. Doesn't seem to dump any errors I can find. This is a fresh install of the docker and server files. If you were not aware of this I just wanted to make sure you were and see if you had any tips.

I will try that tomorrow and report back.

Hope that's good enough.

10 minutes ago, ich777 said:

I will try that tomorrow and report back.

Hope that's good enough.

Oh thats totally fine. I know how hard this stuff is, just wanted to make sure it is on your radar.

@ich777 Used the unraid console feature and used this command:

 

image.thumb.png.945b93cc1614ec4c25a62dd34dfca3a2.png

 

And it didn't get stuck. Weirdly enough it didn't work when I edited out the start-server.sh file to include these flags.

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.