ich777

This should not happen, at least it does not over here, I will take a look at it. If you experiencing any further issues please let me know.

Please force an update from the container again (Docker page -> enable Advanced View -> Force Update at the container -> disable Advanced View again), I think you pulled a broken build that was online for about 5 minutes yesterday.

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"

@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: 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‘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.

Did you also create the file for the password? I don‘t know how ProtonVPN works but you maybe have to edit the config file so that it doesn‘t ask for the password.

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

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.

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

I would strongly recommend that you read the descriptions from the variables in the template: You can also join @Spectral Force's Discord server, he helps me out with 7DtD support: Click

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.

I don't know since this question is specific to Firefox not the container itself, I would recommend that you ask this on the Firefox forums. If you do a quick Google search for something like "open new tab in firefox form command line" you'll find lot's of topics about that.

Yes, it should now be fixed and no additional modprobe should be needed anymore.

I‘m assuming you are using the linuxserver.io container correct? Did you follow the second post in this thread to add you GPU to the container?

No, if it has a plug for external power you have to connect it.

Please post your Diagnostics.

Yes, because they changed something in the driver and the field where @SimonF reads the value has now a different name and that's why it doesn't work anymore. He already knows about that and that's why he told you that you have to change the files, if it doesn't work he has to make different changes. Please give him a bit so that he can go through why it isn't working and provide you another fix for the files to test. Also keep in mind that he does this in his free time and no one pays him for that so to speak you have to be a bit more patient.

This is also working on bridge network.

Please don't do that, that won't work. In my case that does work just fine: If someone without my key tries to connect it fails and is rejected. BTW, this is basically the same as: -k _ (please note that the Rust client will most of the times fall back to the official key server and the connection won't be established through your hbbs <- Server or hbbr <- Relay) EDIT: You can also easily see this in the container log because your key will be actually displayed with this option when hbbs and hbbr are starting.

I'm not sure if that's possible...? Does Google Drive support SSH? You can always use rclone (plugin) to mount your Google Drive to a local path (eg: /mnt/remotes/GoogleDrive) on your Unraid Server and then mount this path inside the Docker container with the option R/W Slave.

You mean you don't have it correct? Simply add a variable with the Key: ROOT and as Value: true <- this will do the job just fine.

Set this to true in the template:

This is a pretty controversial thing, please make your own opinion on this by searching something like: "acpi_enforce_resources=lax hardware risks" on your favorites search engine. Hope that helps too.

I've found a change in RC7 which maybe causes this, already contacted Tom about that.

Intel GPU Top should append the arguments that you've added to the sysllinux.config but you have to try. I can always modify the plugin so that you can append things there.