I should have clarified what I meant with the 2GB figure. I am counting the memory consumption of everything: running Linux (specifically Fedora Server 38), run

I should have clarified what I meant with the 2GB figure. I am counting the memory consumption of everything: running Linux (specifically Fedora Server 38), running k3s (which means CoreDNS, Klipper, Traefik, ...), running the oauth2-proxy, then running the whole suite of Jitsi (sans Jibri, since I do not need the functionality it provides). I simply ran "free -h" in my server and saw 2GB of memory usage. The "actual" amount of memory that goes into running jvb and jicofo seems to be roughly 600 MB, which is still a lot to some, I guess. But I was able to run a meeting with three people and share my screen with peak memory usage at 2.2 GB -- again, for the whole system. k3s-server makes up nearly half of the 2 GB idle figure, sitting at about 700 MB of usage (according to the top(1) command I ran for this post). If 2 GB idle memory usage is too much, then I would say ditch k3s entirely and handle everything with docker-compose, using Nginx as your reverse proxy. That should at least bring the figure down to about 800 MB (jvb, jicofo, prosody, containerd, oauth2-proxy, nginx).