October 20, 20169 yr Hi, After upgrading to 6.2.1 the dockers I have installed want to be updated and some of them did update, however some of them didn't. For example Plex is not updating and it gives me the following error; Error: layers from manifest don't match image configuration. Anyone know what that means? Thanks!
October 20, 20169 yr Well described bug, have a look at the docker faq in the stickies in the docker forum.
October 20, 20169 yr Author Hmm, no I haven't...however after reviewing the instructions they seem a little extreme. I'll give it a shot...I hope I don't need to reconfigure all my dockers...that would be a very sad day, night and day. Below are the instructions given... ------ What do I do when I see 'layers from manifest don't match image configuration' during a docker app installation? I have a theory as to why this is actually happening, unfortunately I am unable to replicate this issue so I cannot test the theory. As to the solution, you will need to delete your docker.img file and recreate it again. You can then reinstall your docker apps through Community Application's Previous Apps section or via the my* templates. Your apps will be back the exact same way as before, with no adjustment of the volume mappings, ports, etc required. This is a one-time operation.
October 20, 20169 yr however after reviewing the instructions they seem a little extreme.While it seems to be extreme, its actually not, and the net time required to get back up and running like nothing happened is ~ 5 minutes (assuming that you're not on a dial-up internet connection) (And its a hell of a lot simpler than doing it on a per-container basis (since multiple containers are going to require the same fix), not to mention that you completely avoid the command line. http://lime-technology.com/forum/index.php?topic=40983.msg499594#msg499594) - as an aside, this is because of changes implemented at dockerHub, not because of an issue with unRaid per se. So long as you re-add the apps via CA's previous apps section, the templates will already be filled out for you the exact same way that they were running before.
October 21, 20169 yr Author Well thats strange, for some reason only one of the dockers I'm using shows up under the CA's previous app selection. Is there a way to create a template from an existing docker?
October 21, 20169 yr Author Oh, I see. According to ***OFFICIAL GUIDE*** Restoring your Docker Applications in a New Image File, you can select 'my-insert docker name here'. Does that seem right?
October 21, 20169 yr Oh, I see. According to ***OFFICIAL GUIDE*** Restoring your Docker Applications in a New Image File, you can select 'my-insert docker name here'. Does that seem right? Yeah, but the list of my-insert docker name here that the guide refers to is the exact same list that CA utilizes. (Myself, and probably a ton of other users here never bother with the drop down list and instead use CA to display everything) If the template drop-down list when adding a container (docker tab) shows more user templates (the my templates) than CA is showing in the previous apps with no docker containers already installed, then can you zip up and either post or PM me the contents of config/plugins/dockerMan/templates-user on the flashdrive. If CA matches the drop down list, then either you've deleted the templates from that folder, or there's a problem with the flash drive saving those templates, or there's a bug within unRaid that no one has noticed yet.
October 21, 20169 yr Here's an explanation from erics about why upgrading to 6.2 may cause grief with existing docker Containers: Docker migrated to a newer API / storage backend for all the Docker containers almost a year ago and has been maintaining the old and new backends up until a couple months ago. The problem was the 'layer ids' that made up Plex, for example, in the old backend didn't match the same layer ids for Plex in the new backend, even though the contents were the same. So time went on and we kept pushing out updates for our Plex container. Eventually the old backend stopped getting the Plex updates when Docker stopped maintaining the old backend. At that point, unRAID 6.1 (older version of Docker), would use the old backend to pull down layers. So when you pulled down Plex initially it used the layer ids from the old backend. Some of the layers, like ubuntu, are probably even "shared" with other installed containers. When you upgraded to unRAID 6.2 (new Docker version) there were now updates available for Plex because the new backend was being used by default. The Plex update, now coming from the new backend, only needed to pull down a couple of the updated layers. It skips the ubuntu base layer because it's already installed but that's the problem since the ubuntu base layer (and possibly other intermediate layers in Plex?) have the old layer ids but the new Plex container expects all layers to have ids from the new backend you get a Error: layers from manifest don't match image configuration Instead of deleting the docker.img, you could alternatively fix this issue by deleting any other container that shares a layer or base image with Plex, essentially purging out layers with old ids, but it's a little tricky to tell which containers do (or maybe all?). So much easier to delete the docker.img and be done with it... at least until Docker decides to migrate to another backend/API again
October 21, 20169 yr Author Ah, thanks for the explanation! However I've confirmed that the template drop-down list when adding a container (docker tab) shows more user templates than CA is showing in the previous apps. I don't understand what you mean by 'with no docker containers already installed' though. I've attached the xml's. CA is only showing Crash Plan Desktop (which isn't used), Handbrake, SageTV, Ubuntu-xrdp, Ubuntu-mail server and Zoneminder. So CA is missing 5 of the 11. I really appreciate the help! Archive.zip
October 21, 20169 yr My guess is the ones that are missing you installed before CA had the feature to track them.. Might be wrong.
October 22, 20169 yr I don't understand what you mean by 'with no docker containers already installed' though. What I mean is that if the app is installed (running or not), it is no longer a "previous" app, and doesn't show up there. It instead appears within the installed apps. Reviewing the thread, it appears that you actually haven't deleted your docker.img file yet Well thats strange, for some reason only one of the dockers I'm using shows up under the CA's previous app selection. Is there a way to create a template from an existing docker? so this behaviour is to be expected. Once you delete the image file, you'll see CA populating the list fully (as no docker apps will be installed) (btw, I extracted those templates, and threw them onto to my secondary server which does not have docker running on it, and they all do indeed appear within the Previous Apps section)
October 22, 20169 yr Author lol! Wow, I'm a dork...you're right. It wouldn't show up under previous apps. I'll give it a try, thanks for the help!
October 22, 20169 yr Might be wrong. You are I know, was hoping you wouldn't notice as I knew you'd say something, haven't you got anything better to do? Doesn't CA need another update today?
October 22, 20169 yr I know, was hoping you wouldn't notice as I knew you'd say something, haven't you got anything better to do? Doesn't CA need another update today? lol Actually when I started that other project, it was a toss up between it and another module that I've been planning out in my head for CA. And before anyone complains, from this point onwards, new modules for CA are going to be separate installs.
October 22, 20169 yr Worked perfectly, thanks again! One day CA will work so perfectly, he'll stop updating it daily....
October 22, 20169 yr Worked perfectly, thanks again! One day CA will work so perfectly, he'll stop updating it daily.... Can't stop when there are feature requests pending http://lime-technology.com/forum/index.php?topic=40262.msg492534#msg492534 http://lime-technology.com/forum/index.php?topic=40262.msg492538#msg492538 Every single feature req is valid, and if they fit within CA's mission will get integrated eventually, and since bonienl himself (the king of kings) suggested them, I think that they should get prioritized. Or, alternatively I could always reissue RepoUpdate (and upgrade it to be 6.2 compatible) and you'll never have to worry about it again.
October 22, 20169 yr If you reinstate repo update I can promise that I will never moan once, on principle, hell I might even do all my dockers via command line just to prove a point... Sent from my LG-H815 using Tapatalk
Archived
This topic is now archived and is closed to further replies.