Skip to main content

Container update status

GET 
/apps/updates

Required role: viewer. An account or token with the viewer or admin role can call this operation.

Example request
curl --request GET \
  --header "Authorization: Bearer $HOSERVA_TOKEN" \
  "https://$HOSERVA_HOST:8008/api/v1/apps/updates"

What the daily registry check last found for each container's image: a new build of the same tag (new_build) is reported apart from a newer version tag (new_version, named by availableTag). The check asks each registry for manifests and tag names only, never a pull. skipped means the registry was rate limiting requests and is asked again at the next check, failed that the check could not tell (including a registry whose saved credential cannot be used or was refused: it is never asked anonymously instead), and not_checked that no check has reached the image yet or that it could not look: the registry wants a login and no credential is saved for it (putRegistryCredential) or the container is pinned to an image digest, so there is no tag to update. The message says which. None of them means up to date. available is false, with no error, whenever Docker itself is not reachable.

Responses​

One entry per container, sorted by name.