ich777

Das kommt mit 6.13.x inklusive VM cloning. Bin noch immer kein Fan von ZFS für den Heimgebrauch aber okay, da muss man sich wohl fügen...

What are your current settings? Do you habe Valheim+ or BepInEx enabled? Is this a mod? If yes try to disable it entirely and test again.

Have you enabled Validate? If yes, disable it. Because that's up to you, I can't answer all questions especially customizing your server. Please also note that I've marked the container as BETA because there is no official statement on private servers from Valve currently for CS2 (strictly speaking currently you even don't need a token for CS2 private servers because they are simply not ready).

A bit more information on your configuration would be nice, can you maybe post your Diagnostics so that I can see why it is not working?

Ich hab deinen Post mal in den Deutschen Bereich verschoben.

Do you mean you need /dev/net/tun in the container? If yes then append this to your config: lxc.cgroup2.devices.allow = c 10:200 rwm

Yes. The containers that use directory will still be using directory, where the new set up ones will use ZFS. Depends on what you are doing with it, it can come in handy when you are planing on doing snapshots with the LXC built in snapshot feature. No, but the real answer is a bit more complicated. It is possible but I would not recommend it, it would be better to re-create them from scratch. This is also on the to do list, haven't had got time yet. I recently removed the red text from the settings page or at least display it only when someone has set it to /mnt/user/... I've now added a help text to the settings page. The new backing storage type comes in handy if you want to use for example the LXC built in snapshot feature (not from ZFS itself <- read a few posts back, someone had an issue with snapshots with ZFS but I can't reproduce that but I'm assuming that he took the snapshots with the ZFS Master plugin and not with the LXC snapshot function, I tried to reproduce in the post above yours).

Don‘t do that. Please only open UDP ports! EDIT: I forgot, you can also skip the check: Click

This is not possible, please read the description from the container again: It is recommended that you create dedicated Steam account for your dedicated servers with the games in it and SteamGuard completely disabled! Simply create a secondary Steam account for your game servers, disable SteamGuard entirely (and make sure that you’ve click on play CS2 once so that this account has the game in its library) and use this account for your game servers. USERNAME and PASSWORD in the Docker template.

@Roalkege so now I've tested it, I completely wiped my cache drive and formatted it with ZFS and put my LXC directory in /mnt/cache/lxc/: I then created two containers for testing: Then I queried the LXC directory (looking good so far with all the configs in there and also the rootfs): After that I looked up all datasets: Then I did a reboot just for testing if everything is still working after a reboot: Then I've created two snapshots, one from Debian, then one From Slackware and then again one from Debian: And everything seems still to work fine: I really can't help with snapshotting within the ZFS Master plugin however if you are taking snapshots with the ZFS Master plugin I would recommend, at least from my understanding, that you leave LXC in Directory mode because you are taking a snapshot from the directory/dataset. The ZFS backing storage type is meant to be used with the built in snapshot feature from LXC/LXC plugin itself. EDIT: I even tried now tried another reboot with the snapshots in place and everything is working as expected:

Please let me test this on my servers if I can reproduce that, maybe something isn't working properly.

The DNS container was created with a directory and not with ZFS correct? I will try this later on my server and see if I can reproduce this. EDIT: Okay so I looked at your Diags and I see that it was created from ZFS, have to try this again on my server, strangely enough your paths point to the dataset created by the plugin and not to the LXC path which was the opposite on my server.

@FailX & @Mainfrezzer the container will be available in the next few hours in the CA App. Please note that this container needs a Steam account provided with SteamGuard completely disabled! It is recommended that you create dedicated Steam account for your dedicated servers with the games in it and SteamGuard completely disabled! DON'T DISABLE STEAM GUARD ON YOUR PRIMARY ACCOUNT!!!

What happens when you issue: nvidia-smi from a Unraid terminal, do you see the temps?

In general, no, Nvidia breaks the temperature readings with each new generation of graphics cards for older cards (even new ones aren't correctly working some times). Depending on what card you are using (no Diagnostics, no further information provided) it is most likely the case that the temperature isn't reported from nvidia-smi

Enable the advanced view in the top right corner of the Docker page click force update and then disable the advanced view again.

I will look into that.

I have not looked into that. Is it now available to the public?

I don't know, I would recommend that you visit the support page from your motherboard and see if your CPU is listed as compatible or if there is any additional information. You Diagnostics show that only the integrated ASPEED GPU is activated: 09:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150] (rev 06) Subsystem: Super Micro Computer Inc AST1150 PCI-to-PCI Bridge [15d9:1c48] 0a:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 52) DeviceName: ASPEED Video AST2600 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1c48] Kernel driver in use: ast Kernel modules: ast I would rather recommend that you double check in the BIOS if you have set your iGPU to the Primary Graphics output and/or if you can deactivated the integrated one in the BIOS or with a dedicated jumper on the motherboard itself.

I've tested it now: On my test server I installed luckyBackup: Then I clicked console: There I typed in: cat /luckybackup/.ssh/ssh_host_rsa_key.pub and got this: There simply mark the whole lines starting from ssh all the way to the last line and click the right mouse button once and click copy from the context menu to copy the contents: Mark only until the end and then close the window. Then open up a terminal from you main server with this icon: There type in: nano ~/.ssh/authorized_keys In nano right click somewhere on the black free space and select past from the contextmenu: Next you have to press on your keyboard: "CTRL + X" followed by "Y" followed by "ENTER" <- this will safe the file After that I created a test directory on my main server with a file in it /tmp/test/testfile.txt Then I opened the WebUI from luckyBackup on my test server and created the test sync: (please note that you have to create the folder on the destionation if it not exists! <- I would also recommend to click "Do NOT create extra directory" which I did afterwards, otherwise you will end up with another folder called test) The I clicked on Advanced and set up the key file: (please be sure to select this exact file and set it up as source) Then I selected the sync and clicked start: Here you can see that the sync from my main server to the test server was successful: Here I made also a screenshot where you can see that the test file is now also available in the correct directory on my test server: Hope that helps. BTW, you only need one instance from luckyBackup (in my case on the test server) because you are connecting directly to the server itself if that isn't clear.

How did you try to update? Did you click the force update button?

Sorry for the inconvenience and thank you for the report, I've redefined the download routine and version check on start from the container. Please update the container itself.

Thaha, not the best project to begin with... Go to - Settings - Management access and enable the ssh server

Try to reboot your system please. Can you please tell me why did you created a dataset and in which path exactly that you created it?

Because you overwrote the container with the dataset (at least that's what I assume). In the Diagnostics from above I only see the DNS container and no second container, the visible container was just a leftover since the container was started but did do nothing anymore because as said, you've overwrote it with the dataset. Look into your lxc default directory if there is a folder in there for your missing container, if not you are sadly enough out of luck. Please don't mess with the lxc default path. This directory should not be touched! EDIT: I would recommend that you set up the built in Backup function and create a backup from each container from time to time since those are not removed, even if you remove the container (...or mess up the directory).