You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use docker compose to deploy jellyfin. When I mount tmpfs to /config/cache/transcodes, I notice that all the owners and groups of the /config/cache directory in jellyfin are abc, and only the owner and group of transcodes are root, and the permissions are drwxrwx---,which causes ffmpeg to have no permission to access the transcodes directory.
This is an inconsistent behavior. For newly created folders, some are owned by root and some are owned by abc. For folder permissions, some are drwxrwx--- and some are drwxr-xr-x, which will lead to confusing permission problems.
I suggest using some kind of script to automatically configure the owner and permissions of the newly mounted folder when jellfyin is initialized to avoid permission problems. Or recheck the code related to owner and permission configuration.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
I use docker compose to deploy jellyfin. When I mount
tmpfs
to/config/cache/transcodes
, I notice that all the owners and groups of the/config/cache
directory in jellyfin areabc
, and only the owner and group of transcodes areroot
, and the permissions aredrwxrwx---
,which causes ffmpeg to have no permission to access the transcodes directory.This is an inconsistent behavior. For newly created folders, some are owned by root and some are owned by abc. For folder permissions, some are drwxrwx--- and some are drwxr-xr-x, which will lead to confusing permission problems.
I suggest using some kind of script to automatically configure the owner and permissions of the newly mounted folder when jellfyin is initialized to avoid permission problems. Or recheck the code related to owner and permission configuration.
Expected Behavior
No response
Steps To Reproduce
Environment
- OS: TrueNAS SCALE 24.10 BETA.1 base Debian 12
CPU architecture
x86-64
Docker creation
Please see "Steps To Reproduce".
Container logs
The text was updated successfully, but these errors were encountered: