Jump to content


Photo

Docker on OMV 3 - Library Access

openmediavault Docker Linux Server

Best Answer Luke , 30 June 2017 - 02:47 AM

Well the issue is the server is unable to execute those files, so either they don't exist, or the server does not have access to execute them.

Go to the full post


  • Please log in to reply
8 replies to this topic

#1 kentish OFFLINE  

kentish

    Member

  • Members
  • 13 posts
  • Local time: 05:29 PM

Posted 29 June 2017 - 04:55 PM

Hi 
 
I could do with some help on this as I'm confused. Installed Open Media Vault version 3 on my NAS, then installed the docker plugin and downloaded the Emby image and set up some shares to the media library. Emby starts fine, can scrap the media and the UI is super responsive however it won't play anything - tried via the web app / dlna and xbox one app - which is confusing as I've had all the working before and I believe I've set things up the same way and everything worked fine. 
 
Attached the docker and server logs.

 

The server is using MergeFS with all libraries owned by root / user and set to 777, Docker is in Host mode with the /config folder sitting on a SSD again controlled by a OMV Share.

 

I'm controlling the docker image via the OMV plugin UI 

 595568da7c4b9_OMVDockerPlugin.png

 

Not sure what i'm missing. Hope some can shed some light on what I'm doing / have done wrong.

 

Kentish 

Attached Files



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152597 posts
  • Local time: 01:29 PM

Posted 29 June 2017 - 10:24 PM

does this file exist?

 

/config/ffmpeg/20170308/ffmpeg



#3 kentish OFFLINE  

kentish

    Member

  • Members
  • 13 posts
  • Local time: 05:29 PM

Posted 30 June 2017 - 02:16 AM

Morning Luke

 

Yes, /srv/dev-disk-by-label-Applications/Emby is mapped to /config

 
root@openmediavault:/srv/dev-disk-by-label-Applications/Emby/ffmpeg/20170308# ls -l
total 89148
-rwxrwxrwx 1 mark 1000 45680536 Jun 28 22:17 ffmpeg
-rwxrwxrwx 1 mark 1000 45594200 Jun 28 22:17 ffprobe
root@openmediavault:/srv/dev-disk-by-label-Applications/Emby/ffmpeg/20170308#
 

Should these been owned by root:users rather than mark:1000


Edited by kentish, 30 June 2017 - 02:20 AM.


#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152597 posts
  • Local time: 01:29 PM

Posted 30 June 2017 - 02:47 AM   Best Answer

Well the issue is the server is unable to execute those files, so either they don't exist, or the server does not have access to execute them.


  • kentish likes this

#5 kentish OFFLINE  

kentish

    Member

  • Members
  • 13 posts
  • Local time: 05:29 PM

Posted 30 June 2017 - 03:00 AM

Ok, got to get to work now, thanks for the pointer

 

I'll check the user permissions when I get back later tonight and see if I can sort it out. Suspect I'll end up creating a specific account for user emby and set the folder to that.

 

Will update the post after.

Cheers and have a good day (it's 8 here in the uk   :) ) off on the school run!



#6 kentish OFFLINE  

kentish

    Member

  • Members
  • 13 posts
  • Local time: 05:29 PM

Posted 30 June 2017 - 05:22 PM

Update, seems that OMV doesn't want to run binaries on a shared folder / drive. Moved the FFMPEG binaries to root of the system drive and they executed the help message which they didn't do on the share..

 

Swapped the server transcoding setting to use system installed version and the everything seems to play fine on the devices I've tested. So the kids will be happy  :D

 

I'll have a read on the OMV to see if this expected behaviour (which I'm guessing it is)  and will most probably create a ffmpeg folder on the OS drive and share that with the docker container. That way I can at least run the latest version of FFMPEG.

 

Cheers Luke for pointing me in the right direction, I was sure it Emby was unable to access the media not that it couldn't run the binaries.



#7 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152597 posts
  • Local time: 01:29 PM

Posted 30 June 2017 - 05:23 PM

Thanks for the feedback.



#8 kentish OFFLINE  

kentish

    Member

  • Members
  • 13 posts
  • Local time: 05:29 PM

Posted 01 July 2017 - 09:25 AM

Update 2:
 
it seems that noexec is set in /etc/fstab when system boots, so removing this from the applications SSD

/dev/disk/by-label/Applications /srv/dev-disk-by-label-Applications ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2

removes the problem


Edited by kentish, 01 July 2017 - 09:27 AM.


#9 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152597 posts
  • Local time: 01:29 PM

Posted 01 July 2017 - 12:47 PM

Thanks for the info !







Also tagged with one or more of these keywords: openmediavault, Docker, Linux, Server

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users