Description
Let's say you pull on monday any Hummingbird image, and on Wednesday a new version is released for the same tag, you may be lacking some CVE fixes.
The Alternative table now would be missleading for example, here the Hummingbird extension is telling me docker.io/library/postgres:18.3 can be replaced by quay.io/hummingbird/postgresql
However, locally I already have quay.io/hummingbird/postgresql but this image has been pulled long time ago; so it contains some CVEs
Solutions
- We could have an
Update button in the catalog.
- We could have an
auto update mechanism in the Hummingbird extension that would update on a configurable basis, the images of the local registry.
Description
Let's say you pull on monday any Hummingbird image, and on Wednesday a new version is released for the same tag, you may be lacking some CVE fixes.
The
Alternativetable now would be missleading for example, here the Hummingbird extension is telling medocker.io/library/postgres:18.3can be replaced byquay.io/hummingbird/postgresqlHowever, locally I already have
quay.io/hummingbird/postgresqlbut this image has been pulled long time ago; so it contains some CVEsSolutions
Updatebutton in the catalog.auto updatemechanism in the Hummingbird extension that would update on a configurable basis, the images of the local registry.