helm VS lsio-mods

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) .

You can setup your environment creating your own docker mod, a docker mod can bootstrap your environment and install your required packages such as kubectl, helm, awscli, etc. Here is an example of my docker mod used to bootstrap my work environment, this mod install the required packages and bootstrap the config files in the container.