5 hours ago
When using network storage, each device is completely unaware of each others users, except the credentials used to authenticate (username/password).
The UID and GID fields are used for controlling which users on the local system are allowed to access the share. If UID 1026 and GID 100 don't correspond to an actual user on the client device (your laptop), then Jellyfin will only have read permissions.
Backing up a bit, DO NOT put /config on a network share. That is a recipe for a very bad time. SQLite, Jellyfin's DB provider, does not tolerate latency well. Even the miniscule latency on a LAN connection.
/config MUST be on a local disk. You should also provide a path for /cache. It isn't strictly necessary, but having static (and local) storage for /cache will help with consistency when you upgrade the container (which will wipe any ephemeral storage).
And going back to the network storage issue. You can either provide an actual user that exists on the laptop in the fstab parameters, and run Jellyfin as that user, or you can remove the UID and GID files and add "noperm" to the options. This will configure the mount to allow all users on the laptop to have read/write access to the mounted CIFS share. Assuming the "username" provided has sufficient access on the server.
The UID and GID fields are used for controlling which users on the local system are allowed to access the share. If UID 1026 and GID 100 don't correspond to an actual user on the client device (your laptop), then Jellyfin will only have read permissions.
Backing up a bit, DO NOT put /config on a network share. That is a recipe for a very bad time. SQLite, Jellyfin's DB provider, does not tolerate latency well. Even the miniscule latency on a LAN connection.
/config MUST be on a local disk. You should also provide a path for /cache. It isn't strictly necessary, but having static (and local) storage for /cache will help with consistency when you upgrade the container (which will wipe any ephemeral storage).
And going back to the network storage issue. You can either provide an actual user that exists on the laptop in the fstab parameters, and run Jellyfin as that user, or you can remove the UID and GID files and add "noperm" to the options. This will configure the mount to allow all users on the laptop to have read/write access to the mounted CIFS share. Assuming the "username" provided has sufficient access on the server.