March 1, 20179 yr 1 minute ago, Squid said: I'm thinking that odd's on its because of "Layers from manifest don't match" that will happen if / when you install another app. Deleting the docker.img is the fix for that, and was because of Docker themselves changing the API used to communicate...(Manifested itself with upgrades from 6.1 to 6.2) Curious. I will run through the exercise again and verify the docker.img file gets deleted. Should have time to do it this week. Thanks!
March 13, 20179 yr On 3/1/2017 at 10:49 AM, harshl said: Curious. I will run through the exercise again and verify the docker.img file gets deleted. Should have time to do it this week. Thanks! I was finally able to run through this again today. Stopped and removed all dockers, including the images for each. Then disabled docker, deleted the docker.img from the GUI, validated it was in fact removed from the CLI, file was not present in /mnt/cache/, which is the referenced path on my server. Shutdown server with docker disabled to add a network card which was unrelated. Fired the server back up, enabled docker with new 20GB image file. From the "Apps" tab, added in one docker that was previously installed, plex from linuxserver.io, checked for update, update was available, processed update, update still available. So the problem still persists. It seems I am the only one hitting this, but there must be a bug of some kind somewhere. Since I don't really even know where to start to look, I will just live with it or purchase some time from the unRAID folks if no one here has any ideas. Thanks! -Landon
March 13, 20179 yr 16 hours ago, harshl said: I was finally able to run through this again today. Stopped and removed all dockers, including the images for each. Then disabled docker, deleted the docker.img from the GUI, validated it was in fact removed from the CLI, file was not present in /mnt/cache/, which is the referenced path on my server. Shutdown server with docker disabled to add a network card which was unrelated. Fired the server back up, enabled docker with new 20GB image file. From the "Apps" tab, added in one docker that was previously installed, plex from linuxserver.io, checked for update, update was available, processed update, update still available. So the problem still persists. It seems I am the only one hitting this, but there must be a bug of some kind somewhere. Since I don't really even know where to start to look, I will just live with it or purchase some time from the unRAID folks if no one here has any ideas. Thanks! -Landon OK one last suggestion on this, if its not this then i really dont know :-). So the docker container that shows as update ready, is it by any chance using a specific tag?, so if you left click the icon in the unraid docker tab webui and select edit and then look at the text field for repository does it have a colon and then some text after it?, if it does have then your pulling a specific tagged image. The webui still has a couple of bugs with this, firstly it always shows the status as update ready, secondly if you click on the update ready link it will then try and download the later image, which of course doesnt exist, so it will return 0 bytes downloaded and will incorrectly show the tag as "latest" in the console output, and will then promptly tell you you still have an update pending, is this your issue?. Edited March 13, 20179 yr by binhex
March 13, 20179 yr 4 hours ago, binhex said: OK one last suggestion on this, if its not this then i really dont know :-). So the docker container that shows as update ready, is it by any chance using a specific tag?, so if you left click the icon in the unraid docker tab webui and select edit and then look at the text field for repository does it have a colon and then some text after it?, if it does have then your pulling a specific tagged image. The webui still has a couple of bugs with this, firstly it always shows the status as update ready, secondly if you click on the update ready link it will then try and download the later image, which of course doesnt exist, so it will return 0 bytes downloaded and will incorrectly show the tag as "latest" in the console output, and will then promptly tell you you still have an update pending, is this your issue?. Great thought binhex, I very much appreciate the response. Unfortunately, I don't see anything like that on any of my docker containers. Below are a couple of examples of the repository and docker hub url settings I have: MariaDB https://registry.hub.docker.com/u/needo/mariadb - docker hub URL --cpuset-cpus=0,4 needo/mariadb - repository TeamSpeak 3 https://hub.docker.com/r/linuxserver/gsm-ts3 - docker hub URL --cpuset-cpus=0,4 linuxserver/gsm-ts3 - repository Bummer deal, sure it weird. Thanks for the ideas though!
March 15, 20179 yr I don't use cpuset myself, but it looks like you need to move it from the "repository" field to the "extra parameters" field. See jonp's comment here:
March 15, 20179 yr 21 minutes ago, ljm42 said: I don't use cpuset myself, but it looks like you need to move it from the "repository" field to the "extra parameters" field. See jonp's comment here: LOL, that did it! During an upgrade that value must not have gotten mapped properly or something. Seemed like a strange place for it, but it dawn on me to move it, duh. I moved the cpuset value from repo down to extra parameters, processed an update and now it shows up to date. Thanks for the catch, much appreciated! -Landon
March 15, 20179 yr 12 minutes ago, ljm42 said: Glad that took care of it! Hey @Squid, is this something FCP could detect? Oh, it looks like FCP already detects this: Extra Parameters for docker App set via Repository instead of Extra Parameters (old style) @harshl - you should install the Fix Common Problems plugin, it probably would have detected this issue for you:
March 15, 20179 yr 1 hour ago, ljm42 said: Oh, it looks like FCP already detects this: Extra Parameters for docker App set via Repository instead of Extra Parameters (old style) @harshl - you should install the Fix Common Problems plugin, it probably would have detected this issue for you: Yup. Pretty much since the beginning. There are however valid cases for putting some parameters in the repository box, but those are container specific options, not general docker parameters
March 16, 20179 yr 22 hours ago, ljm42 said: Oh, it looks like FCP already detects this: Extra Parameters for docker App set via Repository instead of Extra Parameters (old style) @harshl - you should install the Fix Common Problems plugin, it probably would have detected this issue for you: Awesome, I will install it now. Thanks for all you guys do in the community, truly fantastic work! Take care!
Archived
This topic is now archived and is closed to further replies.