Cinerir

The server is starting now, after deleting the WINE64 folder. Thank you a lot. So I would have to delete this folder after every hardware change?

Ryzen 7 5700G, 32 GB RAM, AsRock X570m Pro4. The docker-apps are on an SSD. The dedi GPU (RTX 3050 6GB) is bound to vfio, so shouldn't affect docker. I didn't use the server for a few months, and last month I switched the CPU, before the 5700G I used an 4750G. The only thing that changed since then is the CPU and I guess the server might have gotten a few updates since CE has kinda seasons?

Yes, the 7d2d server is running fine now. The CE server has the same issue as 7d2d had. It restarts constantly. I don't know if/where there are startup-logs of the CE server, but in the continer log it looks pretty much the same. It goes through all the SteamCMD stuff, installs/updates the mods (I also tried it without mods), then writes "server ready", "server starting" and then the window simply closes and the server seems to reboot. Since I wasn't sure if the container log is correct, I just monitored the RAM usage, since the server usually takes up a lot of RAM when it's running. But it barely increased. This is the last thing I was able to copy from the log window before it closed.

God fff.... damnit, I am so stupid. 😫 I am so sorry for wasting your time. Thanks to your pointing me to the output.log I found a line about not being able to find the serverconfig.xml. It confused me and I discovered that I changed the name of the config file in the container setup (was afraid of it being overwritten with an update if it has the standard name), but made a typo while renaming the actual file. I fixed that and now the server doesn't seem to crash, but I can only try to connect to it when I am home. Again, I am really sorry. The problem was me all along, it seems. Doesn't explain why Conan Exiles doesn't start since there is no config-renaming, but for now I am just happy that one thing works again, even though it's my own fault it stopped working.

It looks like this: Is that an okay configuration for the docker-ssd? The output.log writes this: Could this be like an file error from an issue while downloading? I'll set the "validate installation" variable to true and let it check... Thank you for your help, I might join the discord in the evening, when I am back home and can fully focus on it 😃

I open the Log option when right-clicking on the docker icon of the server. There it writes all the steamcmd stuff and then, After this, the log-window simply closes itself. If I re-open it, it starts scrolling through all the steamcmd things again, before closing itself again on the mentioned lines (it's not opening the window with all the lines still there, as if I just closed the window. It is writing/printing the lines again). So I assumed it was rebooting all the time. Server also doesn't show up, I tried connecting via local IP, port forwards are set. I don't have the appdata set to cache, I have a dedicated SSD in the server which is solely for docker-apps. So the path for it is /mnt/docker-apps/appdata/ etc.... I ran the server without issue before the 1.0 update, so maybe it's something in my old config/save, which I then deleted. Am currently reinstalling the 7d2t server again after a server reboot (took the opportunity to de-dust the interior), takes a while due to my connection 😅 I am not a native speaker, sorry if my word salad is all garbled, I hope it makes some sense....

My game servers are also in a boot loop. In my case it's the Conan Exiles and 7 Days to Die server. I am on Unraid 6.12.10. I changed CPU since the last server start, I went from a Ryzen 7 PRO 4750G to a Ryzen 7 5700G. Also put a RTX 3050 in the server, but that thing is bound to vfio and used in a VM, so that shouldn't affect the docker container? I removed and re-downloaded both servers, tried force updating via the docker menu, but they are still boot looping. I thought it might be the steamcmd so I also re-downloaded that one. Didn't help. Quite strange.

Tried it with an Intel Arc A380. Worked like a charm the first time, GPU visible in VM, installed current drivers. No output on monitor plugged into the GPU, but no big issue. After restarting the VM I got the famous error pci header type 127. A full reboot of the host machine solved it, but it comes again after every VM reboot. I guess that's a byproduct of Unraid still not supporting Arc GPUs. Also got a strange error one time, that it was unable to bind it to vfio, but I think that was because it simply didn't detect the card and tried to vfio some CPU stuff to the VM 😂 I'll let the card sit in the host, doesn't make performance worse, I think. And when the Beta branch for the Arc support finally comes, I will give it a try again.

Thanks a ton! Works like a charm. I manually moved a few hundred GB when I switched to this from FileRun (since they discontinued their free version) and it worked perfectly.

And with that my search for a fast, hassle-free and free alternative to Nextcloud continues.... I guess I will have to go back to Filebrowser.