helm VS k3s

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

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod