saarg

Post your docker run command. Did you enable hardware transcoding in the plex settings?

You might be able to change the default folder, but then you have to check out the code-server documentation. This isn't a multiuser software so /config will always be available to the user using code-server. If that feels wrong to you, you have to find another alternative to code-server.

Which GPU do you use? If it's an iGPU, you have to add the chmod command in the go file so it's applied every boot. It doesn't make sense that /dev/dri doesn't exist with the array started. Do you pass through the gpu to a VM?

There isn't really a need to do it this way anymore. If the usb card have its own ID (4 digits:4 digits) then you can stub the card in the syslinux.conf file and then choose the card in the other PCI devices part in the VM template. If the usb card shares an ID with a USB controller on the motherboard, you have to use the new method of stubbing the card using a config file and the PCI number.

Why isn't that correct?

I have to correct you there. We do have a crystal ball, but it's still in the repair shop waiting for the not in stock part.

If you mean the docker log that pops up when you click the log icon in the webui, that is unraids departement. But you can open the log on the command line with timestamp. Might only be possible if you tail the log, but try it out using the below link. https://docs.docker.com/engine/reference/commandline/logs/

You still need the nvidia build to use hardware transcoding with an nvidia card. You probably confused plex hardware decode ability with the need for the nvidia build. If you can't restore the database, your only option is to start from scratch.

No, the settings file for Gitlab. Check the documentation of Gitlab to find the correct file. The one you mention is for reverse proxy and doesnt have anything to do with changing the ports to access Gitlab. You do need to adjust the proxy config if you reverse proxy Gitlab.

Not sure if those cards are still supported by the driver. You also need to install the nvidia plugin and download the nvidia build. For the driver to work, you have to remove the blacklisting so the driver can load.

Not correct. You need to let the container run and it will renew it before it expires. It attempt to renew every night at about 2. When is your cert expiring?

You only changed the port mappings. Gitlab itself doesn't know about those mappings. When you set an IP for the container, the port mappings are obsolete and will be the ones set in the container (Which is the container ports in the template). So to change these to the standard http/https/ssh ports, you need to change the settings file in gitlab.

It's not by default in the template. You can easily add it yourself. The Readme on github is the reference for the correct syntax.

This one of course

Did you upgrade unraid? Sounds like you upgraded to the normal build and not using the nvidia plugin to download the nvidia build.

There is no need to post the same info in two different threads.

Read the link about updating in the first post.

What do you mean by usb pass through the vpn? Do you mean that you want to pass through a usb network adapter to the container?

I don't know how to fix that error.

Not wget. Open the link you posted in a normal browser and you can see all the releases. Then add the correct filename to the link and follow the guide.

Try using /mnt/cache/ or /mnt/diskX/ instead of /mnt/user/ for the app appdata path. Also, please don't restart the application, restart the container. It's the same developer for this as the old version you used.

You should be able to browse for the different versions if you remove the last part of the link.

You can't use the stubbing method you used as all your USB controllers have the same ID. So you need to look at the new method of stubbing using the PCI ID. I don't remember which release it was added, but go through the release announcements to find it. Might have been 6.8, but might have been in one of the 6.7 releases.

The reason is that you have your unraid usb on the same usb controllers that you use vfio-pci.ids on.

Nextcloud was nice enough to include a binary that is glibc only. Since we use alpine and that is musl based, it will not work in our container. They also don't have any arm versions of the binary either as far as I know.