jellyfin

[Unknot]

Hi guys,
I´m running proxmox on Lenovo M720Q with two storage drives (m2+ssd hd) and use Proxmox Script Help to achieve my goals:

• Home Assistant OS (check, LXC working 100%);
• Adguard Home (LXC created but some how still getting stupid ads / banner on mobile apps);
• Immich (LXC created)
• Jellyfin (LXC)

but there's big problem to me: even I mount the SSD on LXC of jellyfish how I put/transfer my media files??? to create library on Jellyfin


thanks in advance

 

[groque]

To make your media files accessible in the Jellyfin LXC, you'll want to bind-mount the SSD path into the container using the Bind Mount Points feature. Once mounted (e.g. to /mnt/media inside the LXC), you can point Jellyfin’s libraries there.

 

[Unknot]

To make your media files accessible in the Jellyfin LXC, you'll want to bind-mount the SSD path into the container using the Bind Mount Points feature. Once mounted (e.g. to /mnt/media inside the LXC), you can point Jellyfin’s libraries there.

I try this but without any success.... my jellyfish server doesn't recognize the media file I have in folder

 

[groque]

I try this but without any success.... my jellyfish server doesn't recognize the media file I have in folder

Can you share a screenshot of the "Resources" tab for your Jellyfin LXC in the Proxmox WebUI? That’ll help confirm if the SSD is properly added as a Bind Mount Point. From what I see, it looks like it might not be set up yet.

 

[Unknot]

Can you share a screenshot of the "Resources" tab for your Jellyfin LXC in the Proxmox WebUI? That’ll help confirm if the SSD is properly added as a Bind Mount Point. From what I see, it looks like it might not be set up yet.

resources shows sda1 as Mount Point (mp0)

 

[groque]

resources shows sda1 as Mount Point (mp0)

It looks like mp0 was added as /dev/sda1 inside the LXC, which is usually used for device mappings. Follow these steps instead:

1.  Remove the wrong mount point
   In Resources → Mount Points delete the entry that maps mp0 to /dev/sda1.
2. If your container is privileged, skip to step 5
3. Add explicit UID/GID mappings to the LXC configuration file
   

   echo "lxc.idmap = u 0 100000 65536" >> /etc/pve/lxc/101.conf
   echo "lxc.idmap = g 0 100000 65536" >> /etc/pve/lxc/101.conf

   This maps the container’s root user and group (UID/GID 0) to UID/GID 100000 on the host.
4. Grant the container access to the SSD directory (Choose one method):
   Option 1 - Change ownership (dedicated folder):
   

   chown -R 100000:100000 /mnt/ssd1

   Option 2 - Use ACLs (keep host ownership):
   

   apt install acl -y
   setfacl -m u:100000:rwx /mnt/ssd1
   setfacl -m d:u:100000:rwx /mnt/ssd1

5.  Create the proper bind mount
   

   pct set 101 -mp0 /mnt/ssd1,mp=/media

   You can change /media to any path you prefer inside the container.
6. Restart the container.
   

   pct restart 101

Now the Jellyfin LXC can access the SSD contents, and you can point its library to /media.

 

[Unknot]

It looks like mp0 was added as /dev/sda1 inside the LXC, which is usually used for device mappings. Follow these steps instead:

1.  Remove the wrong mount point
   In Resources → Mount Points delete the entry that maps mp0 to /dev/sda1.
2. If your container is privileged, skip to step 5
3. Add explicit UID/GID mappings to the LXC configuration file
   

   echo "lxc.idmap = u 0 100000 65536" >> /etc/pve/lxc/101.conf
   echo "lxc.idmap = g 0 100000 65536" >> /etc/pve/lxc/101.conf

   This maps the container’s root user and group (UID/GID 0) to UID/GID 100000 on the host.
4. Grant the container access to the SSD directory (Choose one method):
   Option 1 - Change ownership (dedicated folder):
   

   chown -R 100000:100000 /mnt/ssd1

   Option 2 - Use ACLs (keep host ownership):
   

   apt install acl -y
   setfacl -m u:100000:rwx /mnt/ssd1
   setfacl -m d:u:100000:rwx /mnt/ssd1

5.  Create the proper bind mount
   

   pct set 101 -mp0 /mnt/ssd1,mp=/media

   You can change /media to any path you prefer inside the container.
6. Restart the container.
   

   pct restart 101

Now the Jellyfin LXC can access the SSD contents, and you can point its library to /media.

thank God it works. thank you very much

 

[Unknot]

btw I already have an Western Digital My Cloud 2tb attached my router (RJ45). It's possible add the media files on that external HDD to my jellyfin server?

 

[groque]

thank God it works. thank you very much

Glad to hear it's finally working.

btw I already have an Western Digital My Cloud 2tb attached my router (RJ45). It's possible add the media files on that external HDD to my jellyfin server?

There are a few ways to do this but I believe the easiest would be to mount your NAS on the Proxmox host and then share that mount with the Jellyfin LXC using Bind Mount Points.

Step 1: Add a SMB/CIFS storage in the Datacenter → Storage interface:


Step 2: Add the NAS IP, credentials and share:

Fill in:

• ID: Any name for your storage (e.g. mycloud-2tb)
• Server: Your NAS IP
• Share: The name of the shared on your NAS
• Username/Password: Your NAS credentials
• Content: You can leave this as “ISO image” (don’t worry, you can ignore it and not use it for ISOs)

Proxmox will create a /mnt/pve/your-share-id directory on the host pointing to your NAS.

Step 3: Mount the directory to your Jellyfin LXC
Now that your NAS is accessible from the Proxmox host (e.g. /mnt/pve/mycloud-2tb), you can use the Bind Mount Point feature to mount that path into your Jellyfin LXC, just like you did with your SSD.

pct set 101 -mp1 /mnt/pve/mycloud-2tb,mp=/mnt/mycloud-2tb

Inside the container, Jellyfin will see the NAS content at /mnt/mycloud-2tb, and you can add that path to your Jellyfin library.

 

[Unknot]

Glad to hear it's finally working.

There are a few ways to do this but I believe the easiest would be to mount your NAS on the Proxmox host and then share that mount with the Jellyfin LXC using Bind Mount Points.

Step 1: Add a SMB/CIFS storage in the Datacenter → Storage interface:
View attachment 87866

Step 2: Add the NAS IP, credentials and share:
View attachment 87867
Fill in:

• ID: Any name for your storage (e.g. mycloud-2tb)
• Server: Your NAS IP
• Share: The name of the shared on your NAS
• Username/Password: Your NAS credentials
• Content: You can leave this as “ISO image” (don’t worry, you can ignore it and not use it for ISOs)

Proxmox will create a /mnt/pve/your-share-id directory on the host pointing to your NAS.

Step 3: Mount the directory to your Jellyfin LXC
Now that your NAS is accessible from the Proxmox host (e.g. /mnt/pve/mycloud-2tb), you can use the Bind Mount Point feature to mount that path into your Jellyfin LXC, just like you did with your SSD.

pct set 101 -mp1 /mnt/pve/mycloud-2tb,mp=/mnt/mycloud-2tb

Inside the container, Jellyfin will see the NAS content at /mnt/mycloud-2tb, and you can add that path to your Jellyfin library.

lovely. You are the Master. Works perfectly