docker-mods VS helm

Have you tried adding the OpenCL-Intel Dockermod for the LSIO container? I don't believe it'll function properly without it...fair warning it significantly increases startup time. Additionally, it may not matter if you've already verified your hardware acceleration is working as expected, but at one point I did have to specifically indicate both renderD128 and card0 to get everything settled. If it ain't broke, don't fix it, but that's a difference in our compose files I spotted immediately.

Misc - LinuxServer.io images now support mods with multi-digest layers (https://github.com/linuxserver/docker-mods/pull/577)

Are you using a linuxserver container? If so, check this out as well: https://github.com/linuxserver/docker-mods/tree/jellyfin-opencl-intel

If you are running using the lsio container, you could try out this repo which makes the par2 process 2-3 times faster. https://github.com/linuxserver/docker-mods/tree/sabnzbd-par2cmdline-turbo

If you're using the LinuxServer plex image, you're probably facing this issue. https://github.com/linuxserver/docker-mods/issues/575

Following this issue and looking at the code here it appears that the mod identifies running applications on swag by globbing all the conf files (including samples!) and attemting a connection on them. And it does this with ThreadPoolExecutor(max_workers=100) which seems to explain why those DNS queries were being spammed on pihole.

I run a similar set up, but i run jellyfin with linuxserver's docker with this addon: https://github.com/linuxserver/docker-mods/tree/jellyfin-amd

When using the Nextcloud Helm Charts, how do you execute OCC commands within a Kubernetes the pod? I've tried:

I'm running Nextcloud in Kubernetes, using Nextcloud's Helm Chart. With a default installation (no apps or configuration changes), I get the following errors in the logs:

In each namespace you would deploy a nextcloud instance via whatever method you like. For example, the nextcloud helm chart.

I'm using the official helm chart to install nextcloud: https://github.com/nextcloud/helm

A nextcloud installation (you can install via helm within the same k8s cluster)

There is already a GitHub issue: https://github.com/nextcloud/helm/issues/10

I'm not a Nextcloud expert, but your config file looks okay compared to some instances deployed using the nextcloud helm chart.The resulting config uses APCu for memcache.local ('memcache.local' => '\OC\Memcache\APCu') as recommended in the memory caching documentation.

For nextcloud in particular, what you want can be done. I've seen it done in their kubernetes helm chart (https://github.com/nextcloud/helm) .