Closed Miwer closed 3 years ago
We set that env variable to /config/log when we start Jellyfin, so it's overwriting your env variable.
I have been running into the same problem. I have been trying to migrate from native install to this docker image, but since I cannot set JELLYFIN_CACHE_DIR
, JELLYFIN_CONFIG_DIR
, JELLYFIN_DATA_DIR
and JELLYFIN_LOG_DIR
env variables without having them overridden by the hardcoded settings in the docker image, I will have to add all my libraries and download metadata all over again which is very time consuming. Could you please not hardcode the settings in the image and make it possible to modify the env variables when creating the container?
We don't support all
the env vars jellyfin accepts, because we use some of them to do our automation.
If you're migrating, then move your existing files into the expected locations after creating the container.
My reason for separating the log dir to a volume outside the config dir, is because I don't want my storage snapshots taking up data from the logfiles. I also moved cache and transcode files to a separate storage volume without snapshots. This was configurable from inside jellyfin, but log dir sadly is not. Is it possible to use a symlink in the underlying file system, or will this cause trouble with this image?
We don't support
all
the env vars jellyfin accepts, because we use some of them to do our automation.If you're migrating, then move your existing files into the expected locations after creating the container.
I'm afraid simply moving the files won't be enough since absolute paths are used in the metadata nfo files to point to the image files. If I can't set env vars then is it possible to specify command line options when starting the Jellyfin binary? They can override the env vars.
Both of you can likely use custom mount points to accomplish what you're trying to do.
We have to maintain a balance between customizability and convenience (standardization). We are not trying to provide an image that is highly customizable as it also creates a much bigger support burden for our relatively small team.
If you need to customize further than what we allow, see here: https://blog.linuxserver.io/2019/09/14/customizing-our-containers/
Expected Behavior
Jellyfin should log to the directory specified by environment variable JELLYFIN_LOG_DIR as specified in official Jellyfin documentation: https://jellyfin.org/docs/general/administration/configuration.html#log-directory
Current Behavior
Jellyfin does NOT log to directory specified in environment variable. Environment variables seems hardcoded into docker image.
Steps to Reproduce
add environment variable JELLYFIN_LOG_DIR to docker compose file.
Environment
OS: Openmediavault 5 CPU architecture: x86_64 How docker service was installed: OS provided
Command used to create docker container (run/create/compose/screenshot)
Docker logs