+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: change log file location docker/unraid (/t-change-log-file-location-docker-unraid)
change log file location docker/unraid - gaming09 - 2023-10-19
Trying to change the log file location to a ramdisk from the nvme drive, but i cant seem to get the variable right. I am on Unraid/Docker.
![[Image: 5umvFF6.png]](https://i.imgur.com/5umvFF6.png)
thought it would be this based on the documentation but looks like its writing to the default location still.
RE: change log file location docker/unraid - Deleted User - 2023-10-20
see https://github.com/linuxserver/docker-jellyfin/issues/149
RE: change log file location docker/unraid - gaming09 - 2023-10-20
(2023-10-20, 12:09 AM)000 Wrote: see https://github.com/linuxserver/docker-jellyfin/issues/149
that was closed without resolution?
RE: change log file location docker/unraid - Deleted User - 2023-10-20
if you read it there are 2 pieces of pertinent information
1 - make sure the env path is a path inside the container not on the host
2 - what you are trying to do may not be supported (may not even work)
i didnt feel it was necessary to repeat information that was already available from the source but i suppose i needed to if you didn't get the same points i did
reference - https://github.com/linuxserver/docker-jellyfin/issues/149#issuecomment-1170521891
RE: change log file location docker/unraid - gaming09 - 2023-10-21
(2023-10-20, 05:29 PM)000 Wrote: if you read it there are 2 pieces of pertinent information
1 - make sure the env path is a path inside the container not on the host
2 - what you are trying to do may not be supported (may not even work)
i didnt feel it was necessary to repeat information that was already available from the source but i suppose i needed to if you didn't get the same points i did
reference - https://github.com/linuxserver/docker-jellyfin/issues/149#issuecomment-1170521891
Did a work around set a symlink for the default logs folder to go to the ramdisk, seems to be working but had to chmod 777 which isn't ideal but it's just a logs dir