Oh interesting, didn't think of Graphics drivers getting in the way. It'll go on a Framework laptop, most if not everything should work ootb... ~famous last words~

I have no idea what your experience level is, so I'm saying this just to make sure: DON'T copy this verbatim. The resources bit is what you'd need to adapt into your own compose file. If you have questions, feel free to ask 👍

In case you ran it using a docker run command, read this. Otherwise if you use compose, try something similar to the following:

services:
  service:
    image: nginx
    deploy:
      resources:
        limits:
          cpus: '3'
          memory: 512M
        reservations:
          cpus: '0.25'
          memory: 128M
    cpuset: "1"
    ports:
      - "80:80"

source

If you use some kind of virtualisation and/or containerisation then you can limit ram and/or cpu usage. This can of course greatly reduce lockups if not eliminate them.

Edit: I only now read it's a Pi 3B. Not sure if hosting Jellyfin on that device is a good idea... If you insist though, consider running an LXC inbetween and limit it to three cores. That should leave one core available for the system so the system doesn't lock up again.

Oh yeah you're right, mb

Ayo you got me all hot and bothered there for a second! 😂

For women ~~of childbearing age~~? It DOES.

ftfy

Damn that's a shame

Ayo wtf, that desktop is pretty asf. Well done!

Worth noting that the confinement of Flatpaks and Snaps can have major drawbacks. It has been a major pain in the ass to get Flatpaks working nicely with fractional scaling (think tiny cursor, huge text, tiny text etc etc)

This dude rn