corey 312 Posted March 4, 2016 Share Posted March 4, 2016 I'm struggling to figure out how to update Emby inside a Docker container. I'm running Emby on a Synology DS716+ with Docker 1.6.2 installed. I started with the Docker documentation but I'm getting no where. The Docker documentation for Emby says that I have to install Emby but when I start the container Emby starts up on its own and it doesn't appear to need a systemd service installed. Furthermore the documentation references systemctl but I cannot find that binary when logged into the terminal of the container. I get a: bash: systemctl: command not found Also a find -name systemctl returns nothing Running exec emby-server update from the terminal of the container returns: Usage: /usr/bin/emby-server {start|clear} Thanks for the help! Link to comment Share on other sites More sharing options...
thefirstofthe300 291 Posted March 4, 2016 Share Posted March 4, 2016 It appears that you are attempting to use the helper script which lives on the Docker host and not in the container itself. If you run systemctl enable emby-server on the Docker host, it should work. Also, according to the Emby wiki, updating Emby should be as easy as systemctl restart emby-server.service on the Docker host. 1 Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted March 4, 2016 Share Posted March 4, 2016 (edited) I'm struggling to figure out how to update Emby inside a Docker container. I'm running Emby on a Synology DS716+ with Docker 1.6.2 installed. I started with the Docker documentation but I'm getting no where. The Docker documentation for Emby says that I have to install Emby but when I start the container Emby starts up on its own and it doesn't appear to need a systemd service installed. Furthermore the documentation references systemctl but I cannot find that binary when logged into the terminal of the container. I get a: bash: systemctl: command not found Also a find -name systemctl returns nothing Running exec emby-server update from the terminal of the container returns: Usage: /usr/bin/emby-server {start|clear} Thanks for the help! If your looking to update the emby instance within the container it would be docker run -ti Emby update . If your trying to update the actual container its probably best if you refer to the documentation provided by synology, each NAS manufacture usually provides a means of updating containers which is out of our control. Edited March 4, 2016 by hurricanehrndz Link to comment Share on other sites More sharing options...
corey 312 Posted March 5, 2016 Author Share Posted March 5, 2016 Thanks hurricanehrndz! This is what I executed and it looks like a successful result: ds716nas> docker run -ti emby/embyserver update [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-conf-onetime: executing... [cont-init.d] 01-conf-onetime: exited 0. [cont-init.d] 02-user-onetime: executing... [cont-init.d] 02-user-onetime: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Stopping emby-server... Updating emby-server... All repositories have been cleaned up. Starting emby-server... update exited 0 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. The server version didn't actually update though. Is this related to the 5882 issues I saw in a couple of other threads? Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted March 6, 2016 Share Posted March 6, 2016 There is no update. Suse build service is having issues. So no new packages until that gets resolved. Outside of our control. Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted March 6, 2016 Share Posted March 6, 2016 (edited) Thanks hurricanehrndz! This is what I executed and it looks like a successful result: ds716nas> docker run -ti emby/embyserver update [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-conf-onetime: executing... [cont-init.d] 01-conf-onetime: exited 0. [cont-init.d] 02-user-onetime: executing... [cont-init.d] 02-user-onetime: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Stopping emby-server... Updating emby-server... All repositories have been cleaned up. Starting emby-server... update exited 0 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. The server version didn't actually update though. Is this related to the 5882 issues I saw in a couple of other threads? Its also suppose to be docker exec not docker run. Otherwise its docker pull. Edited March 6, 2016 by hurricanehrndz Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now