Image from MLDonkey is 2 years old, but is the newest , and is marked as available in compose webGUI,
perhaps becaus eis 2 years old?
[Solved] image too old mark as available on OMV-Compose, but not true
-
- resolved
- OMV 6.x
- raulfg3
-
Image from MLDonkey is 2 years old, but is the newest , and is marked as available in compose webGUI,
perhaps becaus eis 2 years old?
This one is updated
GitHub - Wibol/mldonkey-docker: Dockerized mlDonkey 3.1.6 on Ubuntu 18.04 in 90MB image.Dockerized mlDonkey 3.1.6 on Ubuntu 18.04 in 90MB image. - GitHub - Wibol/mldonkey-docker: Dockerized mlDonkey 3.1.6 on Ubuntu 18.04 in 90MB image.github.com -
is marked as available in compose webGUI,
The way it works isn't perfect. It just checks if there is a newer hash available. I don't know how to make it better.
-
-
The way it works isn't perfect. It just checks if there is a newer hash available. I don't know how to make it better.
ok, but because image is not change on 2 years, hash must be the same, so because this , I do not understand that is marked as "available" if is not.
-
Thanks, I check it soon.
-
Thanks, I check it soon.
checked, it's the same version 3.1.6 and have the same "problem", it's marked as image "available" ( not correct because it's the latest:
-
-
ok, but because image is not change on 2 years, hash must be the same, so because this , I do not understand that is marked as "available" if is not.
It is great that you don't believe me... What is the output of:
docker image ls --digests --format "json" logicwar/mldonkey | jq ".Digest"
curl -s https://hub.docker.com/v2/repositories/logicwar/mldonkey/tags/latest | jq ".images[].digest"
it's only a cosmetic bug, no problem if you do not waste time on it.
If the digests from the above commands are different then this is not a bug. It means your system's image is different than what docker hub is reporting as latest.
-
-
So, this image returns a different json format from docker hub for some reason. I guess I will change the plugin to support this but I don't understand why docker hub does this.
-
So, this image returns a different json format from docker hub for some reason. I guess I will change the plugin to support this but I don't understand why docker hub does this.
sorry, not clear different json format.
is not the same?= "sha256:e8bf85ce81c6491e5d68597aa737ac4daf4462ed92b10379cb824929e9a96dca"
-
sorry, not clear different json format.
is not the same?= "sha256:e8bf85ce81c6491e5d68597aa737ac4daf4462ed92b10379cb824929e9a96dca"That is the digest. The digest is the same. The commands I gave you do not return all of the json.
-
-
-
This change is in 6.10.3 in the repo now.
-
-
raulfg3
Changed the title of the thread from “image too old mark as available on OMV-Compose, but not true” to “[Solved] image too old mark as available on OMV-Compose, but not true”. -
votdev
Added the Label resolved -
votdev
Added the Label OMV 6.x
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!