2024-01-26, 02:36 AM
(This post was last modified: 2024-01-26, 03:26 AM by Efficient_Good_5784. Edited 6 times in total.)
Does the BIF file generation work? Is your issue that the scrubbing doesn't appear on the web-player's playback bar?
The reason why your container wont run when you changed the mount was that Jellyfin can't find the files needed to host the web client.
Reading this thread, I assumed the same as @TheDreadPirate thinking that the folder would have been recreated in the host mount.
I'm also running Jellyfin with Jellyscrub on a Truenas Scale server. Revert back the host mount of the jellyfin folder, then just simply run the container as root. That should be enough to get Jellyscrub to inject the script itself into the index.html file.
It's not enough to make a copy of all the files needed for the jellyfin-web folder and host mount it with "jellyfin/jellyfin-web". I could only get the container to run when I copied everything under "jellyfin/" and put that in a host mount to the container.
So if you do want to go the route of not changing your container to always run as root, you'll have to transfer over all the folders and files in /jellyfin into an outside folder, then make that the host mount that'll replace "/jellyfin" in your container.
If you don't want to run the container as root 24/7, you'll have to do the following.
You'll probably want to (or need to) repeat this after each release of a new Jellyfin version in case new things have been added to that folder.
The developer behind Jellyscrub did state some time ago that he's working on integrating it into Jellyfin. So this issue might be solved automatically eventually without needing to do all of this.
I don't know the progress that has been made on this, but I do think that I read that it will be implemented with the release of Jellyfin v10.9.
The reason why your container wont run when you changed the mount was that Jellyfin can't find the files needed to host the web client.
Reading this thread, I assumed the same as @TheDreadPirate thinking that the folder would have been recreated in the host mount.
I'm also running Jellyfin with Jellyscrub on a Truenas Scale server. Revert back the host mount of the jellyfin folder, then just simply run the container as root. That should be enough to get Jellyscrub to inject the script itself into the index.html file.
(2024-01-25, 11:51 PM)jamjellyjam Wrote: Attemp #4: For fun within TrueNAS I mapped it to "/jellyfin/jellyfin-web" and this time it deployed but then automatically stopped. Logs show thatI tried the same thing and figured out what's wrong.
It's not enough to make a copy of all the files needed for the jellyfin-web folder and host mount it with "jellyfin/jellyfin-web". I could only get the container to run when I copied everything under "jellyfin/" and put that in a host mount to the container.
So if you do want to go the route of not changing your container to always run as root, you'll have to transfer over all the folders and files in /jellyfin into an outside folder, then make that the host mount that'll replace "/jellyfin" in your container.
If you don't want to run the container as root 24/7, you'll have to do the following.
- Edit the container to have a host mount to a blank folder. Start the container.
- Through the Truenas App GUI, open the shell of Jellyfin's container.
- Do the following command in the shell: cp -r jellyfin/* [path-to-external-folder-mount]/
- Exit the shell and re-edit Jellyfin's container to use the external folder with the copied contents. Host mount it as "/jellyfin"
You'll probably want to (or need to) repeat this after each release of a new Jellyfin version in case new things have been added to that folder.
The developer behind Jellyscrub did state some time ago that he's working on integrating it into Jellyfin. So this issue might be solved automatically eventually without needing to do all of this.
I don't know the progress that has been made on this, but I do think that I read that it will be implemented with the release of Jellyfin v10.9.