![]() |
Bind mounts on Ubuntu & Docker? - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: Bind mounts on Ubuntu & Docker? (/t-bind-mounts-on-ubuntu-docker) |
RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (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) RE: Bind mounts on Ubuntu & Docker? - theguymadmax - 2025-01-19 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 RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (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. 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. RE: Bind mounts on Ubuntu & Docker? - theguymadmax - 2025-01-19 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. RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (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. RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (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." RE: Bind mounts on Ubuntu & Docker? - theguymadmax - 2025-01-19 Post what you have again for the compose file. RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (2025-01-19, 03:19 AM)theguymadmax Wrote: Post what you have again for the compose file. Code: services: It's giving me that error in regards to the /media/FolderName mount (which we just got all done messing with, with fstab) RE: Bind mounts on Ubuntu & Docker? - theguymadmax - 2025-01-19 Try this instead of the bind for the volumes: Code: volumes: 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-denied-the-path-is-not-shared-to-the-host-when-it-is/142364/2 I run docker not docker desktop, so I don't think I've run into this issue. RE: Bind mounts on Ubuntu & Docker? - 4r5hw45twh - 2025-01-19 (2025-01-19, 03:31 AM)theguymadmax Wrote: Try this instead of the bind for the volumes: Yes, Docker Desktop on Ubuntu. Ok, so if I now try: Code: services: It gives the same error |