ich777

This text should be shown imediately. The first steps are basically that the plugin itslef is downloaded and installed (the GUI part), wich is actually not even 1MB and then the message WARNING is displayed. I really can‘t imagine what‘s going on there, maybe the pull from the version numbers are takig that long but I really can‘t imagine that that‘s the case since this file is only a file with a few KB. Also everything is hosted on GitHub. May I ask where you are located in the world? I have most of the times issues with people living in China that the downloads are really slow and everything takes ages to complete.

I will look into this ASAP and report back, please give me a few days…

On what Unraid version are you? What CPU are you running? Is the appdata share set to use cache only or prefer in the Share settings? What path is specified in the Docker template? EDIT: If you are not already on 6.10.3 then I would strongly recommend to upgrade -> I think this causes actually the issue. If you are on a AMD platform, try to change the path from /mnt/cache/... to /mnt/user/... in the template. <- try this only if you are already on 6.10.3

Ich verschiebe diesen Beitrag mal in den Deutschen Bereich vom Forum. Die sollten automatisch gelöscht werden nach ein paar Wochen wenn ich mich nicht irre.

Sure thing... send me a PM, but I don't think that much will change... I have to wait a little longer for my Deck to arrive since I've preordered a little too late... So I really can't tell what's wrong on the Deck.

Is your server still running? Since you've posted a screenshot from your GameID I've tried to connect but it times out... I've now pulled a fresh copy from the CA App and it works just fine over here. Have you yet tried to validate the game files on your local computer? Maybe the game files are corrupt... If you want me to try to connect to your server let me know and send me the Game ID or at least start the server so that I can try it. You can also try to connect to my server if you want to but I think this is more of a Client side issue in your case. Took a screenshot here:

Sorry but I can't reproduce the issue that you are describing here. I've now installed ArmA3 on my server and both x64 and also the x86 version work and starting just fine: ArmA3 x64.txt ArmA3 x86.txt (attached both logs) Maybe try to remove the container entirely, delete the folder in you appdata directory for arma3 (maybe also try to restart your Unraid server after that) and pull a fresh copy from the CA App.

On what Unraid version are you? Please remove the "TurboVNC Parameters" variable entirely and report back.

I think in some parts of the world GitHub has some issues or something isn't working quite right since it can't pull the latest driver version... Really not sure what to do about that, sorry for the inconvenience...

Why should they? It‘s like if you have them installed on a bare metal machine and the container will only check if a new update is available if a new version is released on container restart (this is also mentioned in the description of the container). If no update is available nothing will be pulled/downloaded. Universal…? Depends on what is universal, you can append „-beta WHATEVERBRANCHYOUNEED“ (also like if you run steamcmd on a regular server on bare metal) to the GAME ID variable. However the usage of branches is always unique to the games itself because every developer uses this a little different. (I think I even put an example in the description of the variable in the container template). Not eveon close I think for the server side, it‘s still a lot but I think we are talking about 35 to 50GB IIRC.

Have to look into things like copy at the end of next month, currently I really don‘t have time to help or develop the plugin further since I‘m real busy in real life. Another idea would be maybe to simply just copy the entire folder for the container and preserve the rights? Just thinking that this should be the easiest solution if it works properly… The plugin is not very polished currently and I‘m really sorry for that but I will definitely continue to improve it after things calmed down a little bit. You should be also able to delete the folder for the Container, this is basically the same as destroying it from the GUI.

Yes, because the plugin uses a existing bridge network. Simply set it in the container according to your Distribution. What would be even easier is to set a static IP for the container in your DHCP server (Router/Firewall).

@VoNpo & @elcapitano just to let you know and because I was also curious, I've now tried it on my test server and it works without a hitch, I've uninstalled the Nvidia-Driver plugin, rebooted my server and pulled a fresh copy from the CA App: (the screenshot shows the installation stage because this takes a little while on my test server, it's not really the fastest machine) This is after it was finished installing: Here you can see my system devices: And here is also a screenshot from the plugin itself:

This wont change anything... You don't need the compiler itself in the container, you only need the runtime libraries that are compatible with the compiler that was used to compiled the binary usually the libraries are backwards compatible because Debian Bullseye is using GCC 10.2.1 May I ask on what Unraid version are you? I will investigate further when I got more time and install it on my server.

How should the Quadro be recognized by the plugin if it‘s bount to VFIO? BIND=0000:0f:00.0|10de:1c31 0000:0f:00.1|10de:10f1 This is something that can't work and you can also see from your screenshot that the driver in use is "vfio-pci" and not "nvidia". 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106GL [Quadro P2200] [10de:1c31] (rev a1) Subsystem: NVIDIA Corporation Device [10de:131b] Kernel driver in use: vfio-pci 0f:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1) Subsystem: NVIDIA Corporation GP106 High Definition Audio Controller [10de:131b] Kernel driver in use: vfio-pci Also why are you on 6.9.2? Unraid 6.10.3 is the most recent version. What also is really suspicious to me is that it seems that you've tried to install the plugin after it's already installed: Jul 8 14:14:33 MASTER root: plugin: skipping: /boot/config/plugins/nvidia-driver/nvidia-driver-2022.05.06.txz already exists Jul 8 14:14:33 MASTER root: plugin: running: /boot/config/plugins/nvidia-driver/nvidia-driver-2022.05.06.txz Please also remove this line from your go file, this should be fixed: # Fix Docker - Case Insensitive sed -i 's#@Docker-Content-Digest:\\s*\(.*\)@#\@Docker-Content-Digest:\\s*\(.*\)@i#g' /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php Please try also the same, run this command from a Unraid Terminal: rm -rf /boot/config/plugins/nvidia-driver and reboot your server afterwards. After the reboot pull the Nvidia-Driver plugin again from the CA App.

If you are using Unassigend Devices to mount the disk/device that you've created would be in /mnt/disks/DISKNAME/lxc and not /mnt/lxc

Stop supportig it and pull it from the CA App. Already wrote above and linked that v2.31 is the latest version for Bullseye. No, because Bookworm uses v2.33

Please post your Diagnostics. Have you any AdBlocking software on your network running? Can you reach GitHub from your local computer? Seems like that your Server can't communicate with GitHub (where the driver package is located). Please remove the plugin entirely and run the command from an Unraid Terminal: rm -rf /boot/config/plugins/nvidia-driver and reboot afterwards. After that try to pull the Nvidia-Driver plugin again from the CA App and see if it is the same (don't close the window with the red 'X' and wait for the Done button to appear). If it's the same it looks like your server can't communicate with GitHub.

What Distro they are using by default? I'm using a Debian Bullseye image and it is of course up do date... Do you need to run it with 64bit? You should always be able to run the 32bit version. Anyways, nothing that I can do about since I'm shipping the default version that is provided by Debian Bullseye and that is version 2.31, see here. If you report that container now as broken I will deprecate it.

Should be possible from what I saw, since I don't own the game I can't create a server for this mod since I have stopped creating game servers for games that I don't own because giving support for such games is a nightmare. If you have a key lying around I'm happy to create a server for you if you are willing to donate it to me...

If you did this then chances are high that you have to add it manually... The best place for this to ask would be their Discord... From what I found on their GitHub page under the Server Host Settings was: Setting: ResetDaysInterval Description: Days between scheduled resets/wipes. When the server starts, and is about to load a save file, it checks if it is time to reset and start a new save file. The previous save file is backed up. Defaults to 0, which means the feature is disabled. Type: number Example values: 0, 7, 14, 37 Overrides: VR_RESET_DAYS_INTERVAL=<value>, -resetDaysInterval <value> (this should be placed in your ServerHostSettings.json file) Hope that helps.

And how did you mount it to /mnt? Anyways, regardles of how did you do all of that, please do it like it is recommended in the support thread and also on the settings page from LXC use something like /mnt/cache/lxc or /mnt/disk2/lxc or you even can mount it via Unassigned Devices and you have to change it something like that /mnt/disks/DISKNAME/lxc I‘ve never had the issue that /mnt/user was missing. Could it be also the case that it‘s probably related to your HBA since you are having issues like you‘ve mentioned above with ZFS too?

Have you yet rebooted after selecting the driver? You have to reboot...

I really don't understand what you are saying here, how can you took a NVME drive and add it as a share?

From what I read so far, everything is uncommon and not related to this. Diagnostics? Very uncommon that this driver caused this. Seems this is an issue with the container and has nothing to do with the driver on the host (this plugin). Sure thing, install Jellyfin add some files to it and let it transcode, you will see that this driver is working, I have tested it, because I test all custom drivers and this one is working just fine... You have to reboot not just simply turn on and off Docker, turning on and off Docker is only for the first installation.