Linux Questions

2414 readers

21 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 2 years ago

MODERATORS

possiblylinux127@lemmy.zip

Podman container doesn't start after system update (pawb.social)

submitted 4 months ago* (last edited 4 months ago) by claymore@pawb.social to c/linuxquestions@lemmy.zip

6 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] claymore@pawb.social 2 points 4 months ago

Alright, thank you very much. Some good resources to get started, and I sorta got somewhere. After an hour trying every option possible and the container still not working, I tried running chown -R serve:serve ~/ as suggested in the reddit thread above. Kind of a nuclear option, but now the container starts! Too bad it stops itself after a few seconds. Honestly considering re-installing the whole OS at this point.