After an automatic update+reboot of my Debian server my Jellyfin container doesn’t work anymore. When I try to run it from the command line I get: Error: crun: make '/home/serve/.local/share/containers/storage/vfs/dir/[string]' private: Permission denied: OCI permission denied

Here’s the list of updated packages, in case it’s useful: base-files buildah curl dns-root-data intel-microcode libc-bin libc-l10n libc6 libcurl3-gnutls libcurl4 libmariadb3 libpam-systemd libpq5 librabbitmq4 libsystemd-shared libsystemd0 libudev1 linux-image-amd64 locales mariadb-common systemd systemd-sysv tzdata udev vim vim-common vim-runtime vim-tiny wget

I tried doing some searching and it looks like a podman issue, but with no real fix for it? Not sure tbh. Do I need to nuke my container and start again? Or is there a way to fix this while keeping my config?

Small update: I did some digging around in the directories that error out and found that in ~/.local/share/containers/storage/volumes both the jellyfin-cache and jellyfin-config folders are owned by 100000, but they were the only ones. I tried changing ownership to my user but the error persists.

  • claymoreOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 days ago

    Yeah I do everything from the serve account. I did try changing the permissions like I said in the edit of my post. What’s confusing me is all my other containers are running fine (Immich, SearxNG, etc.) and it’s only Jellyfin having trouble, if it was a permissions problem none of them should start since their media folders get mounted in that same directory (not an expert on podman, correct me if I’m wrong). I also thought that the images are fine, but it doesn’t hurt to be through. I’ll try changing some permissions around once more later today though.