Install in docker

[talesam]

Could you provide more details on how to install it in Docker?

[BobHasNoSoul]

you will need to mount a volume of the webroot (this depends on container supplier so i cant be super specific) i would guess a volume of /jellyfin/jellyfin-web would be the correct dir

then you edit the parts mentioned in the readme.md depending on your jellyfin version.

[BugZappa]

Steps i took to get this mod to work via docker-compose & the official jellyfin image:

1. Start Jellyfin
2. Make a directory on the host machine, we'll be mounting this directory in Jellyfin as a volume bind.
3. cd into this directory you've made & run this command sudo docker cp jellyfin:/jellyfin/jellyfin-web /Your/Mount/Path

• Replace /Your/Mount/Path with the directory you made in step 2).

• if you run the ls command you should see a directory named jellyfin-web (this is good!)

4. Edit your Jellyfin's docker-compose file and specify this volume:
   
5. Recreate your stack with sudo docker compose up -d --force-recreate
6. Hopefully if everything is done correctly your stack is now online getting its data from your mount path rather than inside your container, you can now follow the Installation steps on the main page..
   

---

[Update] - Persistent storage for the ./avatars path

^^^Be sure to follow the steps above first and have the mod working already.^^^

7. cd into the directory you made in step 2).
8. Make a new directory called ./avatars
9. You're going to want to move the contents of the avatars folder to this new one. -- sudo mv /Your/Mount/Path/jellyfin-web/avatars/* /Your/Mount/Path/avatars
10. Modify your docker-compose.yml file and specify this volume.
    
11. Recreate your stack with sudo docker compose up -d --force-recreate

This way if your Jellyfin updates you won't have to re-pull all the images from the repository and just modify the necessary files.

Shout out BobHasNoSoul for the information!

[Masterpayneio]

Would this prevent Jellyfin from properly updating? I can imagine that /jellyfin-web is often modified when there's a new release

[BugZappa]

Would this prevent Jellyfin from properly updating? I can imagine that /jellyfin-web is often modified when there's a new release

Hm, I'm not entirely sure. I'll have to look into this.

When I initially set out to get this mod to work I was hoping Jellyfin would automatically rebuild /jellyfin/jellyfin-web when specified in the docker-compose.yml file - it didn't and it prevented Jellyfin from starting which in turn lead me to copying out the files from the container to the host machine.

If I encounter any issues I'll definitely edit my original post.

[BobHasNoSoul]

It doesn't stop it from updating however it will remove the mods automatically on updating due to the nature of docker images

…

On Sat, 2 Nov 2024, 06:02 BugZappa, ***@***.***> wrote: Would this prevent Jellyfin from properly updating? I can imagine that /jellyfin-web is often modified when there's a new release Hm, I'm not entirely sure. I'll have to look into this. When I initially set out to get this mod to work I was hoping Jellyfin would automatically rebuild /jellyfin/jellyfin-web when specified in the docker-compose.yml file, it didn't and it prevented Jellyfin from starting which in turn lead me to copying out the files from the container to the host machine. If I encounter any issues I'll definitely edit my original post. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFPTXLH7CO6QBO5XVXOSVG3Z6RTH5AVCNFSM6AAAAABLPZTUISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHA4DGMJWHE> . You are receiving this because you commented.Message ID: ***@***.***>

[BobHasNoSoul]

You could* in theory set the avatars directory as a volume in the compose file so it points to /jellyfin/jellyfin-web/avatars:/path/to/avatars/folder Then all you have to do is modify the files outlined inside the readme I could make a script to do this if needed but it would be per version (and I don't do this full time because I have a job and kids) The script would essentially just download the full files inside the container from my GitHub

…

On Sat, 2 Nov 2024, 08:51 Antony Edwards, ***@***.***> wrote: It doesn't stop it from updating however it will remove the mods automatically on updating due to the nature of docker images On Sat, 2 Nov 2024, 06:02 BugZappa, ***@***.***> wrote: > Would this prevent Jellyfin from properly updating? I can imagine that > /jellyfin-web is often modified when there's a new release > > Hm, I'm not entirely sure. I'll have to look into this. > > When I initially set out to get this mod to work I was hoping Jellyfin > would automatically rebuild /jellyfin/jellyfin-web when specified in the > docker-compose.yml file, it didn't and it prevented Jellyfin from > starting which in turn lead me to copying out the files from the container > to the host machine. > > If I encounter any issues I'll definitely edit my original post. > > — > Reply to this email directly, view it on GitHub > <#3 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFPTXLH7CO6QBO5XVXOSVG3Z6RTH5AVCNFSM6AAAAABLPZTUISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHA4DGMJWHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[BobHasNoSoul]

okay fully pushed a new update to it so it should now be fixed, please confirm when you get a chance

[Professorvennie]

Hi I am trying to follow this with Jellyfin installed using portainer. When I run this command: sudo docker cp jellyfin:/jellyfin/jellyfin-web /Your/Mount/Path it just creates an empty folder named jellyfin-web.

[BugZappa]

Hi I am trying to follow this with Jellyfin installed using portainer. When I run this command: sudo docker cp jellyfin:/jellyfin/jellyfin-web /Your/Mount/Path it just creates an empty folder named jellyfin-web.

Hm, I'm going to be honest with you. Building stacks & containers with Portainer works, but really isn't recommended.

With that being said, I would verify that 1) the containers name is actually called jellyfin (containers will default to some random name if not defined), 2) the files exist within the jellyfin container, you can enter the container by running sudo docker exec -it jellyfin bash and cd or ls the jellyfin root folder /jellyfin.

Apologies for the poor formatting, writing this on my phone.

[Jerrys-modz]

Hi I am trying to follow this with Jellyfin installed using portainer. When I run this command: sudo docker cp jellyfin:/jellyfin/jellyfin-web /Your/Mount/Path it just creates an empty folder named jellyfin-web.

Hm, I'm going to be honest with you. Building stacks & containers with Portainer works, but really isn't recommended.

With that being said, I would verify that 1) the containers name is actually called jellyfin (containers will default to some random name if not defined), 2) the files exist within the jellyfin container, you can enter the container by running sudo docker exec -it jellyfin /bin/bash and cd or ls the jellyfin root folder /jellyfin.

Apologies for the poor formatting, writing this on my phone.

Thank you! I ran the command again and it worked this time. Not sure what happened before I ran it a couple times