2025-06-02, 01:49 PM
TL;DR: I'm trying to narrow down an issue where Jellyfin does not recognize a directory that I created on a Ceph storage mount running in a VM on a Proxmox cluster.
My first thought is that this is a problem with permissions, but I'm not sure where to go from here, since they seem correct. The Proxmox and Ceph subreddits indicate that everything should work based on what I described. ¯\_(ツ)_/¯
What would you suggest?
I have a Debian 12 VM on Proxmox VE with user
I can read and write to this Ceph pool from the VM CLI as this user.
Jellyfin is running via Docker on this VM using the yams script (https://yams.media). Under this same user, the yams setup script was able to write to
Jellyfin cannot read or write to this pool when attempting to configure a Library through the web interface -
My first thought is that this is a problem with permissions, but I'm not sure where to go from here, since they seem correct. The Proxmox and Ceph subreddits indicate that everything should work based on what I described. ¯\_(ツ)_/¯
What would you suggest?
I have a Debian 12 VM on Proxmox VE with user
gadgetboy
(1000:1000). In the VM I've mounted a Ceph pool (media
) using the Ceph linux client at /mnt/ceph
I can read and write to this Ceph pool from the VM CLI as this user.
Jellyfin is running via Docker on this VM using the yams script (https://yams.media). Under this same user, the yams setup script was able to write to
/mnt/ceph/media
and created a directory structure for media management. The PGID:PUID for the yams script and the resulting Docker Compose file match the user.Jellyfin cannot read or write to this pool when attempting to configure a Library through the web interface -
mnt
appears empty when traversing the file system through the web interface./mnt/ceph
is obviously owned by root. /mnt/ceph/media
is owned by gadgetboy
.