danioj Posted February 6, 2016 Share Posted February 6, 2016 Ah. OK. Seems like the ports are still available from the outside world... they are just mapped one-to-one... 8096 --> 8096 and 8920 --> 8920. Another question, when I set up this new container, I was not able to modify the default host mapping of /mnt, i.e. couldn't change it to /mnt/media... After adding the container, it now appears that I can edit it. Any idea why? You can edit default mappings of each container before, or after install. Not sure what stopped you when you installed BUT it is not my experience that this is a design feature of unRAID. Not being able to edit default mappings on install would really suck and I am sure many users would be up in arms if that was the case. Either way I don't see this as an issue with unRAID nor this Docker. It is certainly something I have not seen reported before nor experienced for myself. Perhaps Browser issue? *Shrugs*. Quote Link to comment
hurricanehrndz Posted February 6, 2016 Author Share Posted February 6, 2016 I have definitely experienced this myself with many containers on chrome. Quote Link to comment
CHBMB Posted February 6, 2016 Share Posted February 6, 2016 I have definitely experienced this myself with many containers on chrome. Me too.. Quote Link to comment
huladaddy Posted February 6, 2016 Share Posted February 6, 2016 Interesting. I'm using Pale Moon. I'll try restarting my browser if I have that problem again... Quote Link to comment
mata7 Posted March 3, 2016 Share Posted March 3, 2016 hi can someone please help me out im getting this message Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5881 is now available for download i shutdown and restart the server but nothing update, i shutdown the emby server from unraid and nothing get update, can someone please tell me how update it? thanks in advanced Quote Link to comment
danioj Posted March 3, 2016 Share Posted March 3, 2016 hi can someone please help me out im getting this message Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5881 is now available for download i shutdown and restart the server but nothing update, i shutdown the emby server from unraid and nothing get update, can someone please tell me how update it? thanks in advanced - Go to your unRAID Web GUI. - Click on "Docker" Tab. - Click on "Check For Updates" Button at the bottom of the "Docker Containers" section of the web page. - In the third column (Version) of the row containing Emby, "up-to-date" will have changed to "update ready" and will now be a link. - Click "update ready" link. - A popup will appear asking for confirmation that you want to execute the update. - Click "Just do it!" button. - A dialog box named "Updating Container" will appear to show you the progress of the update. Just wait and let it run. - When finished (It can take a while as the updates can be a couple of hundred MB) you will see a statement in the dialog box saying "The command finished successfully!" and a button called "done" (you "might" have to scroll down slightly) will appear at the bottom of the dialog. - Click the "done" button and the dialog will dissapear. The Emby Docker container will restart and apply the new config. Done Quote Link to comment
mata7 Posted March 3, 2016 Share Posted March 3, 2016 mine docker are updated, thas the problem i update at ready and even reboot the server, i click check for update and mine say is updated, thanks for you help Quote Link to comment
Omnicrash Posted March 3, 2016 Share Posted March 3, 2016 Yup, same problem here: docker is updated, but Emby still claims to need an update. Quote Link to comment
danioj Posted March 3, 2016 Share Posted March 3, 2016 Right, I see what you guys are reffering to: Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5881 is now available for download. Please shutdown the server and update manually. Running on http port 8096, and https port 8920. This is not an issue with the docker container though IMHO. Some Docker Containers (like the ones supported by the linuxserver.io group) are designed to always run the latest version and when you start them they pull the latest files from the selected repositories when you start/restart them. This is not the case with Emby I think. Each time a new version is released it appears the container needs to be updated and pushed out for that new version. What it looks like is the Emby community has pushed out an update and there hasn't been a corresponding update to the Container yet. This can happen if the release group is very frequent with releases. Plus it's a dependency on the maintainer of the Container and I don't think we can expect instant updates. I wouldn't worry though. Unless you have a specific issue that the new release is going to address then relax. An update to this container to match the latest version will get pushed out quite soon. It's usually very quick in my experience. Quote Link to comment
mata7 Posted March 3, 2016 Share Posted March 3, 2016 thank you very mucho, i will wait then Quote Link to comment
Omnicrash Posted March 3, 2016 Share Posted March 3, 2016 It's strange though, because there was a container update roughly at the same time I got the update notification, so I expected it to include the update. Quote Link to comment
danioj Posted March 3, 2016 Share Posted March 3, 2016 It's strange though, because there was a container update roughly at the same time I got the update notification, so I expected it to include the update. I agree it is strange - and I might be wrong in my assessment - but I don't think I am. Without asking the Emby team for confirmation (which I could do via their forum if you guys want me to) I think it more likely they pushed out an update. Container got updated. Emby team quickly found something minor was wrong and pushed out another (which of course is not common) to fix. Quote Link to comment
hurricanehrndz Posted March 3, 2016 Author Share Posted March 3, 2016 Updates are nearly automatic. Unfortunately though the docker depends on linux packages and sometimes the openSUSE build service has some issue. https://build.opensuse.org/project/show/home:emby Quote Link to comment
mata7 Posted March 3, 2016 Share Posted March 3, 2016 im sorry im a little slow, so you mean the packages have some issue, is anything i have to download from that link? sorry my english is no that good just want to make sure, my docker packages is Author:emby dont know that help thanks Quote Link to comment
hurricanehrndz Posted March 3, 2016 Author Share Posted March 3, 2016 Nope you do not need to download. Information only. Yes packages have issue. Quote Link to comment
mata7 Posted March 3, 2016 Share Posted March 3, 2016 thank you very much, really apreciated you help Quote Link to comment
JonathanM Posted March 5, 2016 Share Posted March 5, 2016 Where do you set the permissions for the metadata that Emby downloads? It's currently 0644, which causes issues. Quote Link to comment
danioj Posted March 5, 2016 Share Posted March 5, 2016 Where do you set the permissions for the metadata that Emby downloads? It's currently 0644, which causes issues. What issues are you reffering to? Quote Link to comment
JonathanM Posted March 5, 2016 Share Posted March 5, 2016 Where do you set the permissions for the metadata that Emby downloads? It's currently 0644, which causes issues. What issues are you reffering to? SMB client can't move or delete the files until permissions are changed to 0666. Quote Link to comment
hurricanehrndz Posted March 5, 2016 Author Share Posted March 5, 2016 There is no such setting within emby or the docker. Perhaps the issue is with the owner of the files. I could perhaps try and encorporate such a thing in future updates within the docker via an environment variable Quote Link to comment
mata7 Posted March 6, 2016 Share Posted March 6, 2016 im still having the same problem, hurricanehrndz do you have any idea when this is gone get fix? thanks in advanced Quote Link to comment
hurricanehrndz Posted March 6, 2016 Author Share Posted March 6, 2016 It's not in my hands. We use the opensuse build service. When suse gets around to fixing it is when it will get fixed. Quote Link to comment
Capt.Insano Posted March 6, 2016 Share Posted March 6, 2016 My Emby Server Dashboard reports: Current Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5882 is now available for download. Please shutdown the server and update manually. Running on http port 8096, and https port 8920. Any chance of triggering an updated container build? Thanks as always hurricane!! Edit: Sorry, misunderstood above posts!! Question removed! Thanks! Quote Link to comment
BRiT Posted March 6, 2016 Share Posted March 6, 2016 It's not in my hands. We use the opensuse build service. When suse gets around to fixing it is when it will get fixed. My Emby Server Dashboard reports: Current Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5882 is now available for download. Please shutdown the server and update manually. Running on http port 8096, and https port 8920. Any chance of triggering an updated container build? Thanks as always hurricane!! Capt.Insano, please read the immediate post above yours. Quote Link to comment
Capt.Insano Posted March 6, 2016 Share Posted March 6, 2016 It's not in my hands. We use the opensuse build service. When suse gets around to fixing it is when it will get fixed. My Emby Server Dashboard reports: Current Version 3.0.5871.0 A new version of Emby Server is available! Version 3.0.5882 is now available for download. Please shutdown the server and update manually. Running on http port 8096, and https port 8920. Any chance of triggering an updated container build? Thanks as always hurricane!! Capt.Insano, please read the immediate post above yours. Thanks BRiT, I have edited my post. I misunderstood what was said before my last post! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.