2025-03-31, 12:46 AM
You are possibly right this is not a Jellyfin bug (probably), but how do I determine what is causing this issue? k8s or nixos, I have doubts about both because under the hood, i am using docker, or containerd which iirc is the runtime for docker, and unless jellyfin is using some host resource, then that error would be completely within the container and a issue with the image itself, do you think jellyfin is using some host resource or something that goes beyond its contaniner which might be worth me investigating?