satchafunkilus

Just updated to the latest version. The docker compose changes work nicely, from what I can tell. Thanks a lot for fixing this!

No for compose containers you would usually update them by running "update stack" on the compose manager site. I don't think you can apply an update to compose containers from the normal view. Also in the folded out view it does not show the "apply update" for compose containers - as you see here: All the paperless containers are compose containers, and for some reason, it is showing updates available for 3 of them, when in reality there are none. Just looking at the screenshot now, I noticed that the ones that are indicating an update are from dockerhub, whereas paperless-ngx is from ghcr.io. Might have something to do with that....

Well if it would work correctly, I would love to have orange text on update for compose containers. If it's broken (and can't be fixed), I would much rather have the compose containers excluded from the orange highlighting alltogether.

The issue with compose is not necessarily solved by hiding the update column. Compose containers often times get highlighted in orange, to indicate an update, when there really is none. Of course, you can disable the highlighting in the folder settings, but then you break the update highlighting of normal docker containers in the same folder.

There seems to be an error in the template: The path mapping for the database is pointing to /root/.evcc in the container, where the correct path should be /.evcc/

Yes, they were ticked before and after the upgrade. I also tried unticking them and activating them again. Once I unticked them, the software transcoding worked. When I had them checked, it was just a black screen and not working. And I also always had the PLEXCLAIM variable added.

I don't think it's an issue with the linuxserver image, since I had the same problem with the binhex plex container. So my guess is rather some issue happening when upgrading from 6.8 to the 6.9 beta with an existing plex container.

I switched from binhex plex to binhex plexpass and was able to keep everything as is. Just changed the name of the image to pull from dockerhub. I'd expect that it should work switching from a different image as well.

If you read through the thread just a couple of posts above, you'll notice multiple users reporting the same issue. Switching to binhex plexpass container seemed to fix the issue for everyone so far...

Sounds pretty similar to my issue with the binhex plex container. After switching to binhex plexpass everything worked fine.

The plugin is not compatible to 6.8.3, you'll need the latest beta release 6.9.0-beta35 for this to work.

Thanks a lot @ich777 for all your work! Already reached out to @ich777 via PM, but adding this here to see if someone is experiencing the same issue: I upgraded to 6.9.0-beta35 from the 6.8.3 nvidia kernel with hardware transcoding working in all containers (Plex, Jellyfin, etc.). After successful installation of the nvidia-plugin, the graphics card is showing up in settings and nvidia-smi, but I am unable to get hardware transcoding to work. As soon as I activate hardware transcoding in Plex, I get a black screen instead of the video. Software transcoding works fine. Already tried uninstalling the plugin and reinstalling it, rebooted multiple times, removed and added the variables for the containers, to no effect. Anyone else experiencing the same issue or any idea what could be the problem? --------- EDIT: I have managed to get hardware transcoding to work in Jellyfin, but still no luck with Plex... EDIT2: Switching docker-images from binhex/arch-plex to binhex/arch-plexpass did the trick. Hardware transcoding is working flawlessly now. Thanks @ich777!

I am getting the exact same error message. MariaDB is running on IP X.X.X.11 and I have set the environment variable accordingly (DB_HOST and CMD_DB_URL like stated in the config.json). Still, the error message is showing that codimd is looking for the database on the IP X.X.X.26 (which is the IP address for the codimd container). Any ideas anyone?