ich777

This is not possible that you get the same log output since it doesn't try to connect to a FTP server by default. Attached the log output from a untouched template: log-firststart.txt log-secondstart.txt

Yes. Where is the log?

You just can click on the Container icon and then on Log. Seems like it can‘t connect to the specified FTP server… Have you yet tried to let everything at default in the template and then try it again? What you can also do is that you mount the FTP server through Unassigned Devices and then mount this directory in the Docer template from DirSyncPro, don‘t forget to mount it with R/W Slave when adding it in the template.

Without the log I can't tell much...

Have you changed any of the settings in the template or better speaking did you turn on validation? I would recommend to give the xml another file name that already exists in there and change the name for the xml in the template too, with this way you are making sure that the file doesn't get overwritten. Anyways, I would also recommend that you join @Spectral Force's Discord over her, he helps me out with 7DtD: Click

Can you be a bit more precise? What exactly needs an update?

I will look into that shortly and report back. EDIT: I have now changed the Download routine again and found a few bugs that should now be resolved. Please update the plugin to version 2022.08.04 and try to download the driver again. The reason behind this is that I've completely overhauled how the Update & Download button works because for the upcoming changes fro 6.11+

No, If you got the error message like the other users simply go to the download page and click Update & Download, then it should download the driver properly. When it downloaded it correctly in the first place you see that it only verifies the checksum and it says that everything is okay you can reboot.

No worries, glad that it is now solved for you! May I ask if you had to do anything else other then uninstall the NerdPack including the packages and reboot or did you do anything else?

@Scootter I was somehow able to reproduce your issue on my test server but not on my main server. This maybe sounds really stupid but to solve the issue I simply copied the GPU UUID from the plugin again in the template at NVIDIA_VISIBLE_DEVICES and clicked Apply again and the container is now running again... This also survives reboots too. Don't know what caused this, maybe it was the up and downgrades that I've did on my test server...

Have you rebooted in between installing the drivers? This usually indicates that the runtime is not working properly and also is logged in your syslog. What packages have you installed from the Nerd Pack? I can only imagine that you have something installed that is interfering with the Nvidia Driver. Have you changed anything recently in your system, may it be the hardware or software (Docker, Plugins,...) Which script? It should be enough, if you use your card only for Docker container to append: nvidia-persistenced to your go file, no script needed.

Recently there where made a few necessary changes for 6.11+ and on how the plugins works (download, detection on available versions, paths to the packages) and I‘ve simply made a few trivial mistakes so that this was happening. Sorry for the inconvenience...

Can you provide a bit more information please (Screenshot from your plugin page, Screenshot from the Error message, Diagnostics). Does the version numbers display? I can imagine a few things that happened on your system but it should work just fine.

@danimal86 & @Bearco have found an bug please execute this from a Unraid terminal and click the Update & Download butten after executing the command: rm -rf /boot/config/plugins/nvidia-driver/packages/$(uname -r | cut -d '-' -f1) I will fix this ASAP so that this won't happen the next time you try this.

I will take a quick look at this, give me a bit please. Have to downgrade to 6.10.3

Please post a screenshot from your plugin page. Which driver did you choose?

?

Diagnostics? On what plugin version are you? Please make sure your plugin is up to date. Tried it now and I have no issue at all:

No, I deprecated everything related to check-mk because I won‘t support it anymore because of this post: If you really want to you can install it manually with that link: https://raw.githubusercontent.com/ich777/unraid-check-mk-agent/master/check_mk_agent.plg

Sorry that it took so long, pushed now an update where it always falls back to the installed version if the latest version or your preferred version can't be fetched.

Simply add that as a environment variable in your Docker template and it should work. This is also doable with a variable in your Docker template, but I have to look into that how to install it. Users have reported that with this added fonts everything is working: ttf-wqy-zenhei fonts-wqy-microhei fonts-takao fonts-arphic-uming fonts-noto-cjk The terminal is a whole different story usually, can you enter chinese fonts a Unraid terminal? This is maybe a issue from luckyBackup and QT itself that I'm maybe not able to fix if it's built without support for that fonts.

Then why not use his container if it’s working for you?

I can only tell you that on ArmA3 not all mods work on Linux and since DayZ is from the same publisher it is most likely the case… Also keep in mind that this game was only available for Windows for a long time.

This is actually related to containerd… Anyways glad it is fixed for you with 6.11

I would not believe everything, there is also more too it sometimes... Does this user even run Unraid? Docker officially supports cgroup2 since Docker v20.10 and this version was included in 6.10.0 and the release date was: 2022-05-07 Yes, exactly, because the control groups are assigned to cgroup1 and you simply can't change the control groups when they are still in use, but as said you can run cgroup2 on Unraid as you can see here: of course everything else is running too like Emby and so on... As said above I haven't tested everything but as far as I can tell everything seems to be working fine. This is also not the proper way to do it, I would always recommend rebooting when messing with the cgroups