Jump to content

Docker


Luke

Recommended Posts

hurricanehrndz

Nothing special, and it seems odd to me. Perhaps it's the specific video you are testing. Please post your htop and ffmpeg logs for both scenarios we will be able to see if we are really comparing apples to apples

 

Sent from my D6603 using Tapatalk

Link to comment
Share on other sites

fantaxp7

Nothing special, and it seems odd to me. Perhaps it's the specific video you are testing. Please post your htop and ffmpeg logs for both scenarios we will be able to see if we are really comparing apples to apples

 

Sent from my D6603 using Tapatalk

Ok thanks. I will do so, once I figure out VM's on unraid. 

 

Perhaps I can have my friend test out other videos in the mean tine.

 

Thanks

Link to comment
Share on other sites

Capt.Insano

Just a quick Docker question:

 

Is the frequency of Docker container builds on purpose or accidental?

 

5655e7c07e097_Capture.png

 

 

7+ builds in the last 24 hours?!!

 

My unRAID box is constantly alerting my to Emby updates with no real update to be found contained within!!

 

 

Just curious!!

 

 

As always, thanks for the great work!

Link to comment
Share on other sites

fantaxp7

Nothing special, and it seems odd to me. Perhaps it's the specific video you are testing. Please post your htop and ffmpeg logs for both scenarios we will be able to see if we are really comparing apples to apples

 

Sent from my D6603 using Tapatalk

I'm going to chalk it up to the specific video, it was a full blu ray, folder style. I've had a few users connect and transcoding hasn't been too ridiculously high, only a spike in cpu up to 60-70 every once in awhile, then back to 13ish.

 

Thanks

Link to comment
Share on other sites

witteschnitte

Hi. Short question. i tried to use docker on CentOS. but if i try to start i get

 

{datapath} includes invalid characters for a local volume name

I think it is the / in the path. but i tried to use exact the same as the emby guide provide

 

{datapath}:/config

 

do you have any ideas?

Link to comment
Share on other sites

witteschnitte

I like to migrade from the CentOS installation to docker. can i put my /var/lib/emby-server folder anywhere to use with docker? So that i dont have to build everything new?

 

Regards

Link to comment
Share on other sites

mediaGuy

Latest (emby:latest) update seems to have broken something.  Can't reach the server and now all I get is:

"Cannot open assembly '/usr/lib/emby-server/MediaBrowser.Server.Mono.exe': No such file or directory" in my Docker log

 

I re-downloaded the full image and get the same thing,

Edited by mediaGuy
Link to comment
Share on other sites

mediaGuy

I see all the files are actually in /usr/lib/emby-server/bin but the runsv script points to /usr/lib/emby-server

 

Should I just modify the script?

 

-------------------------------------------

 

Edit, gave it a try, emby starts-ish now but the log tells me it can't find my user database.  Nothing's changed in my system - config share is as it has always been.

Edited by mediaGuy
Link to comment
Share on other sites

hurricanehrndz

Yes, docker will have major updates coming down the pipe soon. I will fix the script for now.

 

Sent from my D6603 using Tapatalk

Link to comment
Share on other sites

hurricanehrndz

Docker build was just triggered to fix the issues. Which version of the docker image are you running by the way?

Edited by hurricanehrndz
Link to comment
Share on other sites

mediaGuy

I'm using the stable (latest).  Just tried a pull, nothing there yet, I guess it's not finished building.

 

Just went to grab my log and started digging more.  I'm guessing you've changed permissions a bit because I ended up having to grant additional permissions to the docker config share and now it's running properly.

Link to comment
Share on other sites

hurricanehrndz

Okay, perfect. Yeah, apparently docker didn't pull the new build files from github. I have retrigger a new build. No there has been no permission changes done whatsoever. If you do run docker exec though sometimes individual can inadvertently apply changes to files unknowingly 

Link to comment
Share on other sites

  • 2 weeks later...
pianogamer5

Quick question on basic functionality: If I do a

docker pull emby/embyserver

would the actual Emby instance inside the container be updated? Or is it just the Ubuntu part of the container? I've had the container for a while and have a cron job set up on my main server to do a

docker pull

every night, but the actual Emby instance is still sitting pretty at 3.0.5781.3, where 3.0.5781.8 was just released. What gives?

Edited by pianogamer5
Link to comment
Share on other sites

hurricanehrndz

Quick question on basic functionality: If I do a

docker pull emby/embyserver

would the actual Emby instance inside the container be updated? Or is it just the Ubuntu part of the container? I've had the container for a while and have a cron job set up on my main server to do a

docker pull

every night, but the actual Emby instance is still sitting pretty at 3.0.5781.3, where 3.0.5781.8 was just released. What gives?

If you do a docker pull everything should get updated. Updates take time to propagate it is not as instant as you would think. 

Edited by hurricanehrndz
Link to comment
Share on other sites

agreenfield1

If you do a docker pull everything should get updated. Updates take time to propagate it is not as instant as you would think. 

 

Are you sure there?  My understanding that to upgrade a container you need to docker pull, stop & delete the existing container, and docker run a new instance?

Link to comment
Share on other sites

hurricanehrndz

Are you sure there?  My understanding that to upgrade a container you need to docker pull, stop & delete the existing container, and docker run a new instance?

Well of course, that is all part of the docker pull. I guess I assumed most people would be aware of that fact.

Edited by hurricanehrndz
Link to comment
Share on other sites

  • 3 weeks later...

Today I executed in the container the update. It showed a message requiring action for replacing /etc/sudoers.d/emby.

I just pressed D for differences and as it delayed so much i think I just also pressed enter key. So it showed differences and took the default action "keep old file" (c'mon!? A default action on intro?)

 

So now how I can update this file and keep changes inside the docker container?

And.... is that supposed to ask for actions or should be an unattended process that could be scheduled?

 

info:

 

Setting up emby-server (3.0.5785) ...

 
Configuration file '/etc/sudoers.d/emby'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** emby (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/sudoers.d/emby 2016-01-04 16:07:34.000000000 +0100
+++ /etc/sudoers.d/emby.dpkg-new        2016-01-10 08:05:34.000000000 +0100
@@ -1,7 +1,37 @@
-#Allow emby to start, stop and restart itself
-nobody ALL=(ALL) NOPASSWD: /usr/bin/sv *
+#Allow emby group to start, stop and restart itself
+Cmnd_Alias RESTARTSERVER_SYSV = /sbin/service emby-server restart
+Cmnd_Alias STARTSERVER_SYSV = /sbin/service emby-server start
+Cmnd_Alias STOPSERVER_SYSV = /sbin/service emby-server stop
+Cmnd_Alias RESTARTSERVER_SYSTEMD = /usr/bin/systemctl restart emby-server
+Cmnd_Alias STARTSERVER_SYSTEMD = /usr/bin/systemctl start emby-server
+Cmnd_Alias STOPSERVER_SYSTEMD = /usr/bin/systemctl stop emby-server
+Cmnd_Alias RESTARTSERVER_INITD = /etc/init.d/emby-server restart
+Cmnd_Alias STARTSERVER_INITD = /etc/init.d/emby-server start
+Cmnd_Alias STOPSERVER_INITD = /etc/init.d/emby-server stop
+
+
+%emby ALL=(ALL) NOPASSWD: RESTARTSERVER_SYSV
+%emby ALL=(ALL) NOPASSWD: STARTSERVER_SYSV
+%emby ALL=(ALL) NOPASSWD: STOPSERVER_SYSV
+%emby ALL=(ALL) NOPASSWD: RESTARTSERVER_SYSTEMD
+%emby ALL=(ALL) NOPASSWD: STARTSERVER_SYSTEMD
+%emby ALL=(ALL) NOPASSWD: STOPSERVER_SYSTEMD
+%emby ALL=(ALL) NOPASSWD: RESTARTSERVER_INITD
+%emby ALL=(ALL) NOPASSWD: STARTSERVER_INITD
+%emby ALL=(ALL) NOPASSWD: STOPSERVER_INITD
+
+Defaults!RESTARTSERVER_SYSV !requiretty
+Defaults!STARTSERVER_SYSV !requiretty
+Defaults!STOPSERVER_SYSV !requiretty
+Defaults!RESTARTSERVER_SYSTEMD !requiretty
+Defaults!STARTSERVER_SYSTEMD !requiretty
+Defaults!STOPSERVER_SYSTEMD !requiretty
+Defaults!RESTARTSERVER_INITD !requiretty
+Defaults!STARTSERVER_INITD !requiretty
+Defaults!STOPSERVER_INITD !requiretty
+
 #Allow the server to mount iso images
-nobody ALL=(ALL) NOPASSWD: /bin/mount
-nobody ALL=(ALL) NOPASSWD: /bin/umount
+%emby ALL=(ALL) NOPASSWD: /bin/mount
+%emby ALL=(ALL) NOPASSWD: /bin/umount
 
-Defaults:nobody !requiretty
+Defaults:%emby !requiretty
 
Configuration file '/etc/sudoers.d/emby'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** emby (Y/I/N/O/D/Z) [default=N] ?
invoke-rc.d: policy-rc.d denied execution of start.
ok: run: emby: (pid 16389) 0s
Edited by Sergio
Link to comment
Share on other sites

hurricanehrndz

Should be an unattended process. I will try and address this. Thank you

 

Sent from my D6603 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...