• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions Bind mounts on Ubuntu & Docker?

    Pages (4): « Previous 1 2 3 4 Next »

     
    • 0 Vote(s) - 0 Average

    Bind mounts on Ubuntu & Docker?

    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #11
    2025-01-19, 02:43 AM (This post was last modified: 2025-01-19, 02:52 AM by 4r5hw45twh. Edited 3 times in total.)
    (2025-01-19, 02:32 AM)theguymadmax Wrote:
    Quote:to the very bottom and save?
    Yes

    Ah, geeze. I saved, tried the umount and mount -a commands on that guide but it wasn't finding the drive from that and gave a hint to reload systemctl or something, so I did. Then just restarted the PC for a clean bootup and now it says, "You are in emergency mode" when trying to boot up Ubuntu.

    Was I supposed to get the UUID of the /sdb or /sdb1? I did /sdb1 since the guide's used the one that ended in "1"

    EDIT: I got back to my Desktop GUI but the drive still mounts at what it was mounting at before. Should I do the disk instead of the partition?
    EDIT2: Actually, shoot. If I do lsblk on /sdb, it doesn't list the fstype nor mountpoint. Only for the partition (/sdb1)
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,009
    Threads: 0
    Joined: 2024 Jun
    Reputation: 58
    #12
    2025-01-19, 02:55 AM
    The easiest thing to do is open up the Disks app. Find your hard drive. Select the largest partition and it will have the UUID number there.

    You'll see
    Size:
    Contents:
    Device:
    UUID:
    Partition Type
    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #13
    2025-01-19, 02:57 AM (This post was last modified: 2025-01-19, 02:58 AM by 4r5hw45twh.)
    (2025-01-19, 02:55 AM)theguymadmax Wrote: The easiest thing to do is open up the Disks app. Find your hard drive. Select the largest partition and it will have the UUID number there.

    You'll see
    Size:
    Contents:
    Device:
    UUID:
    Partition Type

    So I should use that UUID and not the one from Terminal? When I use Terminal, it spits out one (that was posted here already) and looks just how the guide's looks. On Disks app, it's only 16 characters total.
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,009
    Threads: 0
    Joined: 2024 Jun
    Reputation: 58
    #14
    2025-01-19, 03:01 AM (This post was last modified: 2025-01-19, 03:02 AM by theguymadmax.)
    Yes, that one. The guide is wrong it tells you to use the PARTUUID, but you should use the UUID. That number in the disks should match the UUID when you run the sudo blkid /dev/drive command.
    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #15
    2025-01-19, 03:05 AM (This post was last modified: 2025-01-19, 03:07 AM by 4r5hw45twh. Edited 1 time in total.)
    (2025-01-19, 03:01 AM)theguymadmax Wrote: Yes, that one. The guide is wrong it tells you to use the PARTUUID, but you should use the UUID. That number in the disks should match the UUID when you run the sudo blkid /dev/drive command.

    Ohhhhh, ok. Well dang, that would've been nice to know a hour ago, hahaha. Looks like it properly mounted this time. Going to fully reboot and see if it does on a clean reboot just to make sure real quick....

    EDIT: Yep, properly mounted. Nice.
    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #16
    2025-01-19, 03:17 AM
    (2025-01-19, 03:01 AM)theguymadmax Wrote: Yes, that one. The guide is wrong it tells you to use the PARTUUID, but you should use the UUID. That number in the disks should match the UUID when you run the sudo blkid /dev/drive command.

    Ok, so with fstab complete and running the docker-compose.yml command now, I am getting this:

    Mounts denied: the path /media/FolderName is not shared from the host and is not known to Docker."
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,009
    Threads: 0
    Joined: 2024 Jun
    Reputation: 58
    #17
    2025-01-19, 03:19 AM
    Post what you have again for the compose file.
    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #18
    2025-01-19, 03:23 AM (This post was last modified: 2025-01-19, 03:25 AM by 4r5hw45twh. Edited 1 time in total.)
    (2025-01-19, 03:19 AM)theguymadmax Wrote: Post what you have again for the compose file.

    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        user: 1000:1000
        network_mode: 'host'
        volumes:
          - /home/username/Dockers/Jellyfin/Config:/config
          - /home/username/Dockers/Jellyfin/Cache:/cache
          - type: bind
            source: /media/FolderName
            target: /Media
        restart: 'unless-stopped'

    It's giving me that error in regards to the /media/FolderName mount (which we just got all done messing with, with fstab)
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,009
    Threads: 0
    Joined: 2024 Jun
    Reputation: 58
    #19
    2025-01-19, 03:31 AM (This post was last modified: 2025-01-19, 03:39 AM by theguymadmax. Edited 3 times in total.)
    Try this instead of the bind for the volumes:

    Code:
        volumes:
          - /home/username/Dockers/Jellyfin/Config:/config
          - /home/username/Dockers/Jellyfin/Cache:/cache
          - /media/FolderName:/Media
        restart: 'unless-stopped'

    Are you running Docker Desktop?  I think that is the issue you have to share the drive with docker desktop when you set up bind mounts. See this post: https://forums.docker.com/t/mounts-denie...s/142364/2 

    I run docker not docker desktop, so I don't think I've run into this issue.
    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #20
    2025-01-19, 03:36 AM
    (2025-01-19, 03:31 AM)theguymadmax Wrote: Try this instead of the bind for the volumes:
    Are you running Docker Desktop?

    Yes, Docker Desktop on Ubuntu. Ok, so if I now try:

    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        user: 1000:1000
        network_mode: 'host'
        volumes:
          - /home/username/Dockers/Jellyfin/Config:/config
          - /home/username/Dockers/Jellyfin/Cache:/cache
          - /media/FolderName:/Media
        restart: 'unless-stopped'

    It gives the same error
    Pages (4): « Previous 1 2 3 4 Next »

    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode