PhilWhite 64 Posted March 16, 2017 Share Posted March 16, 2017 OK, just wondering, Josh or anyone else who can answer. I haven't moved over to Freenas 10 (Corral) yet, but is there any magic to it? Any issues with Emby in a docker container? I assume our Emby servers in current jails will not transfer, which is not that big an issue -- just means redoing everything. Just wondering if things are ready to go yet? Thanks, Phil Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 16, 2017 Share Posted March 16, 2017 We will be testing this soon, thanks. Link to comment Share on other sites More sharing options...
A_Aron 1 Posted March 17, 2017 Share Posted March 17, 2017 I am attempting to move to Corral this weekend, will either of these work? https://hub.docker.com/r/freenas/emby/ https://hub.docker.com/r/emby/embyserver/ ... or am I doing this wrong? Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 17, 2017 Share Posted March 17, 2017 We haven't tested it yet, therefore we don't have answers right now. Why not try it and report your experience? thanks. ! Link to comment Share on other sites More sharing options...
Middling 3 Posted March 18, 2017 Share Posted March 18, 2017 I moved to Corral a couple of days ago. The Docker version of Emby works fine but i couldn't use my old Jail's config, and had to start from scratch. In theory it should have 'just worked' because i kept my Emby config on an external dataset and mounted it to the jail's /var/db/emby-server directory. Coincidentally i also mounted my media library under /media (which is the Docker container's default), so it should have just been a matter of pointing the Docker container's /config at my external Emby dataset and /media to my media dataset and starting the container. In practise things didn't work out so well. The container came up with all settings preserved and working, but for some reason it must have thought my library didn't exist because it removed all the metadata (though using 'ls' from the Emby container's console showed my library properly mounted in /media). I copied the configs back from a snapshot and tried a few different times with the same result. I even removed the libraries completely and re-added them but Emby refused the scan them. I didn't spend much time trying to debug what had gone wrong because people would be getting back home a few hours later and i didn't want to hear complaints. In the end i just wiped my old config and started from scratch. Use the official FreeNAS Emby Docker image. It pulls from the official Emby image anyway, but the FreeNAS version's Dockerfile contains additional metadata about the container (such as what ports to expose on the host and whether FreeNAS should upgrade the container automatically) which adds functionality. Other than that initial problem everything's been running fine for me. Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted March 18, 2017 Author Share Posted March 18, 2017 Luke and Middling, Thank you. I'll probably be able to get to it by next weekend. I assumed I would have to recreate Emby under the new Docker version anyway, so no big deal there. Link to comment Share on other sites More sharing options...
A_Aron 1 Posted March 19, 2017 Share Posted March 19, 2017 I had a similar issue to Middling, except I was moving from Debian Jessie to FreeNAS. My only gripe is portability, i wish there was an easier way to port/restore your config. I'm slowly rebuilding today. But performance is great so far. I gave the docker host 8 cores, and 16G of ram; which i hope is enough. Link to comment Share on other sites More sharing options...
BloodyIron 24 Posted March 23, 2017 Share Posted March 23, 2017 (edited) Hi Folks, Coincidentally found this thread. First, let me introduce myself. I provide support for FreeNAS, but I don't work for iX systems (the company behind FreeNAS). I provide 3rd party support for FreeNAS and connected systems. This support is free and/or paid support, depending on the situation and the client's needs. I provide support in the IRC channel, and various other forms (the support coverage is international). Second, I want to lend a few of my thoughts here, maybe I can help! I haven't sunk my teeth very deep into FNAS 10 (Corral) just yet, but I've been working with FreeNAS, ZFS and related tech for quite some time, so maybe I can help anyways. So, assuming you're still stuck... Middling, the way you had it setup before, did you configure Emby to store the metadata content in the same space as the media itself? If so, this may be contributing to your conundrum here. Share with us how it was configured before, and after, and maybe that could dig up some tasty bits. Middling, I would also recommend checking the permissions the files list as having when you're looking within the Docker scope. It _SOUNDS_ like the Emby Server may not have the necessary permissions to the files to handle them. In my experience filesystem permissions are one of the first things I check when dealing with a Unix (like) environment. Please let us know what you find. Everyone, it is generally recommend (HIGHLY) that if you are doing any MAJOR FreeNAS version upgrades, that you BACK UP your CONFIGS (within FreeNAS) BEFORE you upgrade. This isn't a magic bullet, but it can save your ass in so many scenarios where you need to roll back. Everyone, if you guys experience any issues that seem to be leaning towards FreeNAS' "fault", it's best that you collect as much info as you can, and share it with the FreeNAS forums. Part of what I do is act as a liaison between myself and various FOSS devs (including iX Systems), so help get things fixed that people care about. Sharing information that you see about problems is part of that process, even if I am not involved. Everyone, Docker is just one way you can run "applications" on the new FreeNAS 10 (Corral). You can also run bhyve VMs, so if you already have an Emby VM setup, perhaps converting the VM image to work on bhyve could streamline any migration you want to do. I have not yet kicked the crap out of bhyve myself, but I know the devs moved towards bhyve and Docker because the Jail system was generally the most "problematic" area for people. As in, normally when I notice someone jumping in IRC for help, the majority of the time it's been about Jail issues. Everyone, if you want to run something like Emby on the same host as FreeNAS, be careful of how much RAM you have in the system. ZFS and FreeNAS doesn't typically take much CPU power, but ZFS leverages RAM very regularly so you don't want to be shortchanging your storage, nor your Docker/VMs at the same time. If you want some more detailed recommendations here, let me know. Hope this helps! It's pretty cool to hear overlap between two awesome FOSS techs in my life Oh, and if you want to pick my brain on such things, just let me know and I'll help you out Edited March 25, 2017 by BloodyIron 1 Link to comment Share on other sites More sharing options...
cybersword 0 Posted March 23, 2017 Share Posted March 23, 2017 (edited) I hate to hijack this thread, but I'm having the exact same issue as Middling after migrating /var/db/emby-server directory to the new Docker container. Initially everything works fine, but after a few minutes (after the first media scan finishes) all content disappears. Before the first media scan, everything works as it should, I can play music, movies, etc. I've double checked the permissions, but they're all in order as well. I did have to mount /config directory as /var/db/emby-server as well though, since i noticed in the logs that it was having errors accessing some images. Additionally, I do not store metadata together with the media. I've uploaded my Emby logs to: http://pastebin.com/iAWXbQnP Edited March 23, 2017 by cybersword Link to comment Share on other sites More sharing options...
Middling 3 Posted March 25, 2017 Share Posted March 25, 2017 (edited) Middling, the way you had it setup before, did you configure Emby to store the metadata content in the same space as the media itself? If so, this may be contributing to your conundrum here. Share with us how it was configured before, and after, and maybe that could dig up some tasty bits. Middling, I would also recommend checking the permissions the files list as having when you're looking within the Docker scope. It _SOUNDS_ like the Emby Server may not have the necessary permissions to the files to handle them. In my experience filesystem permissions are one of the first things I check when dealing with a Unix (like) environment. Please let us know what you find. I've always kept metadata separate from the media. In fact the media directories have always been mounted in the Jail/Docker as read-only because i don't want Emby touching my files. Metadata was stored alongside the rest of Emby's config files in an external dataset that was mounted as /var/db/emby-server when using Jails and /config when using Docker and in both cases had the necessary file permissions. My media datasets were mounted read-only under /media in both Jails and Docker using the same directory hierarchy and also had sufficient permissions. My, uneducated, guess is that somewhere Emby is using absolute file paths and didn't like the config being moved. Anyway, it was only 30 minutes to configure Emby from scratch (plus a few unattended hours to re-download the metadata), and things have been running flawlessly since. Edited March 25, 2017 by Middling Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 25, 2017 Share Posted March 25, 2017 Thanks for the feedback ! Link to comment Share on other sites More sharing options...
Vidman 589 Posted March 30, 2017 Share Posted March 30, 2017 OK I have updated from 9.3 via 9.10 to corral and installed the official FreeNAS emby docker and everything is back up and running ok so far. One question tho how does the docker container system apply updates in FreeNAS 10? Do I enable auto updates in the emby web UI? Or is the container updated and must be applied in the freeNAS UI? Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 30, 2017 Share Posted March 30, 2017 Hi @@Vidman, you would use the regular update method for our Docker install, irrespective of the fact that it happens to be used on freenas. Link to comment Share on other sites More sharing options...
A_Aron 1 Posted March 30, 2017 Share Posted March 30, 2017 Hi @@Vidman, you would use the regular update method for our Docker install, irrespective of the fact that it happens to be used on freenas. Yeah, that doesn't appear to work. I see there was a 3.2.9 update today; I clicked the restart emby button as directed, but it appears as if emby attempted to restart as it kicks off a media scan (i have a scheduled task to scan media at startup) but it still has the message that I need to upgrade. Sadly restarting the docker container, or the docker host doesn't update it either ... Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 30, 2017 Share Posted March 30, 2017 That sounds like all you did was restart the server. You didn't actually update anything. The instructions say to head over to our download page. From there you can click the wiki button to check out our docker wiki. It contains the command used to update. Link to comment Share on other sites More sharing options...
Vidman 589 Posted March 30, 2017 Share Posted March 30, 2017 Ok I think I have it sorted for the official FreeNAS emby docker I set the environment variable EDGE to 1. I think this sets the docker to check and update on restarting. This seemed to update me from 3.2.8 to 3.2.9 and now I'm just waiting for everything to be scanned back in Yeah, that doesn't appear to work. I see there was a 3.2.9 update today; I clicked the restart emby button as directed, but it appears as if emby attempted to restart as it kicks off a media scan (i have a scheduled task to scan media at startup) but it still has the message that I need to upgrade. Sadly restarting the docker container, or the docker host doesn't update it either ... OK I have updated from 9.3 via 9.10 to corral and installed the official FreeNAS emby docker and everything is back up and running ok so far. One question tho how does the docker container system apply updates in FreeNAS 10? Do I enable auto updates in the emby web UI? Or is the container updated and must be applied in the freeNAS UI? 1 Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 30, 2017 Share Posted March 30, 2017 Thanks for reporting back. Link to comment Share on other sites More sharing options...
A_Aron 1 Posted March 30, 2017 Share Posted March 30, 2017 Ok I think I have it sorted for the official FreeNAS emby docker I set the environment variable EDGE to 1. I think this sets the docker to check and update on restarting. This seemed to update me from 3.2.8 to 3.2.9 and now I'm just waiting for everything to be scanned back in Confirmed that worked for me too. Link to comment Share on other sites More sharing options...
Vidman 589 Posted March 30, 2017 Share Posted March 30, 2017 Confirmed that worked for me too.Yep just updated again to 3.2.10 Link to comment Share on other sites More sharing options...
Luke 37010 Posted March 31, 2017 Share Posted March 31, 2017 Thanks for confirming. Link to comment Share on other sites More sharing options...
Vidman 589 Posted April 13, 2017 Share Posted April 13, 2017 (edited) Well that sux https://forums.freenas.org/index.php?threads/important-announcement-regarding-freenas-corral.53502/ Edited April 13, 2017 by Vidman Link to comment Share on other sites More sharing options...
Luke 37010 Posted April 13, 2017 Share Posted April 13, 2017 Change is hard. For them to switch all plugins to docker one can argue they should have made it a whole new product. Link to comment Share on other sites More sharing options...
PhilWhite 64 Posted April 13, 2017 Author Share Posted April 13, 2017 Well, guess I'm glad I waited. Will wait to see what emerges, but I think the switch to docker is probably going to be inevitable. The switch using 9.10 as a base will be easier, though. Link to comment Share on other sites More sharing options...
Marcelo 3 Posted April 18, 2017 Share Posted April 18, 2017 I'm using the docker on Corral and everything is running really well for me. Too bad that I'll have to switch everything again to 9.10.3. But in the mean time I'm having one issue. My androids clients are not showing video and from what I read I have to downgrade the ffmpeg version. I saw the command on the linux docker forum to do it but at least for me is not working on the freenas. Can anyone help me with this please? The command that I'm using is: docker exec -it emby-server bash -c 'zypper --non-interactive in curl; \ ⏎curl -sL https://johnvansickle.com/ffmpeg/releases/ffmpeg-3.1.4-64bit-static.tar.xz | \ tar -C /bin --extract -J --wildcards "*/ffmpeg" --wildcards "*/ffprobe" --strip-components=1' I altered the emby-server to my correct name so that's not the problem. Thanks, Marcelo. Link to comment Share on other sites More sharing options...
Luke 37010 Posted April 18, 2017 Share Posted April 18, 2017 I'm using the docker on Corral and everything is running really well for me. Too bad that I'll have to switch everything again to 9.10.3. But in the mean time I'm having one issue. My androids clients are not showing video and from what I read I have to downgrade the ffmpeg version. I saw the command on the linux docker forum to do it but at least for me is not working on the freenas. Can anyone help me with this please? The command that I'm using is: docker exec -it emby-server bash -c 'zypper --non-interactive in curl; \ ⏎ curl -sL https://johnvansickle.com/ffmpeg/releases/ffmpeg-3.1.4-64bit-static.tar.xz | \ tar -C /bin --extract -J --wildcards "*/ffmpeg" --wildcards "*/ffprobe" --strip-components=1' I altered the emby-server to my correct name so that's not the problem. Thanks, Marcelo. Hi Marcelo. The best thing to do is please discuss an example, and then provide the information requested in how to report a media playback issue. thanks ! 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