Update kind: unknown

[tapufd]

Using image zedred/apcupsd-cgi:latest, but this one show Update kind as unknown. Even tried with labels:

• 'wud.tag.include=^latest$$'
• 'wud.watch.digest=true' But doesn't help. Am I doing something wrong, or is this a bug? Thx, T

[fmartinou]

Hi,

update kind can have the following values:

• tag => that's when you use semver tags (e.g. you're running the 1.0.0 tag and there is a 2.0.0 tag available on the registry)
• digest => that's when you use non semver tags (e.g. latest, which is now pointing to a newer digest on the registry
• unknown => that's often when there is no update available

I've tested with your zedred/apcupsd-cgi:latest image and please find below the JSON saved by WUD

{
  "id":"ec4dc4b729e9e3aa31a5434ed9a491b55ff787950798c03c42e4bd5e0585eff6",
  "name":"apcupsd",
  "status":"running",
  "watcher":"local",
  "includeTags":"^latest$",
  "displayName":"apcupsd",
  "displayIcon":"mdi:docker",
  "image":{
     "id":"sha256:39f2ec89cd4352ea988673bf53bde5e8a31ef848a5db7c280acafb5609b94619",
     "registry":{
        "url":"https://registry-1.docker.io/v2",
        "name":"hub"
     },
     "name":"zedred/apcupsd-cgi",
     "tag":{
        "value":"latest",
        "semver":false
     },
     "digest":{
        "watch":true,
        "repo":"sha256:2ce8b87586b66a7fa97f671f94538ddaa615d8ff2cfa536dec97553085ca2eca"
     },
     "architecture":"amd64",
     "os":"linux",
     "created":"2023-03-03T23:03:45.915Z"
  },
  "updateAvailable":false,
  "updateKind":{
     "kind":"unknown"
  },
  "result":{
     "tag":"latest",
     "created":"2023-03-03T23:03:45.915Z"
  }
}

Here you can see that update_kind is unknown because there is no update ("updateAvailable":false)

Which is the value of the update available property on your end? If it's true, then it's a bug, else it's normal.

[tapufd]

Hi, Thanks for the feedback already. Let me explain what happened... I had the container running and WUD didn't mention there were updates, which was correct. Then a few days ago an update was done of the image, because WUD told me that the container with unknown can be updated to unknown. I didn't understand what was happening, but on docker hub I saw that the image was updated a few days ago. So the warning was correct, except it was strange with the unknown in it. So I pulled the image again, and there was indeed a new latest one. But after updating and using the latest image, WUD still keeps saying there is an update for it. See attached screenshots. But I see now that the digest value (sha256:...) is still different for me, or maybe I'm looking wrongly. However I always pull the latest version, and no new image is downloaded for me. Maybe I should try to get that JSON output from my side... how is that done? /T

[tapufd]

To be 100% sure, I deleted my local image, so that it was forced to download it from the internet. And now suddenly WUD doesn't complain anymore of an update. :-s However, my feeling says that when there is another update done of that latest image, WUD will mention again there is an update available (which is good), but again with the strange unknown in it: "Container apcupsd-cgi running with unknown can be updated to unknown." (which is what I always get when this latest image is updated) /T

[tapufd]

Hi, I have the same problem again:

-> message = Container apcupsd-cgi running with unknown can be updated to unknown.

The trigger is indeed correct: But the message isn't.

I think "unknown" should be replaced with a digest number. Isn't it?