[Not Solved]
Nov 11, 2018, 05:04 PM
(This post was last modified: Nov 11, 2018, 06:32 PM by bzowk.)
Hey Guys -
I need some help getting some of my Docker containers working with media files hosted on a Windows share.
I host my media library on a 43.5tb partition 13 (combined disks using Stablebit DrivePool) on my primary workstation which runs Windows 10. Until recently, I also hosted Plex, Sonarr, Radarr, Lidarr, HeadPhones, NginX, NZBHydra2, Ombi, Tautulli, Jackett, and more as well. I use the same system for many things including work so to help reduce background resource usage I created a dedicated Docker host by installing Project Atomic Fedora 28 on a spare PC and have since been migrating many of these services to it. It's worked out great except for services that require direct interaction with media.
I mounted the share(s) to paths on the Docker host via CIFS with full permissions, then tried to add the share paths as mounted volumes to the containers, but I've found that Docker prevents this behavior.
For example, I mounted my share of music which I then mounted for the HeadPhones container for "/music". I verified that the mounted share was accessible and worked as desired from the host. When trying to start it, I get:
If I remove the mounted path, it starts and works correctly.
I've also tried installing CIFS within the container to mount the share internally, but was not able to do so. The only steps I can find relate to Docker for Windows which I do not use.
Any suggestions would be appreciated - Thanks!
UPDATE
I read that adding the string below will allow mounting within a container so tried it:
--cap-add SYS_ADMIN --cap-add DAC_READ_SEARCH
However, when trying to mount within the container after adding that, I get "no such device". I can ping the host from within the container, verified the shares settings, verified permissions, etc. Any ideas? Thanks
I need some help getting some of my Docker containers working with media files hosted on a Windows share.
I host my media library on a 43.5tb partition 13 (combined disks using Stablebit DrivePool) on my primary workstation which runs Windows 10. Until recently, I also hosted Plex, Sonarr, Radarr, Lidarr, HeadPhones, NginX, NZBHydra2, Ombi, Tautulli, Jackett, and more as well. I use the same system for many things including work so to help reduce background resource usage I created a dedicated Docker host by installing Project Atomic Fedora 28 on a spare PC and have since been migrating many of these services to it. It's worked out great except for services that require direct interaction with media.
I mounted the share(s) to paths on the Docker host via CIFS with full permissions, then tried to add the share paths as mounted volumes to the containers, but I've found that Docker prevents this behavior.
For example, I mounted my share of music which I then mounted for the HeadPhones container for "/music". I verified that the mounted share was accessible and worked as desired from the host. When trying to start it, I get:
Code:
"container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"mountpoint for devices not found\"""
If I remove the mounted path, it starts and works correctly.
I've also tried installing CIFS within the container to mount the share internally, but was not able to do so. The only steps I can find relate to Docker for Windows which I do not use.
Any suggestions would be appreciated - Thanks!
UPDATE
I read that adding the string below will allow mounting within a container so tried it:
--cap-add SYS_ADMIN --cap-add DAC_READ_SEARCH
However, when trying to mount within the container after adding that, I get "no such device". I can ping the host from within the container, verified the shares settings, verified permissions, etc. Any ideas? Thanks