You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We should update all container images to UBI 9.5 to pull in security fixes and other updates.
Describe the solution you'd like.
Currently we are using UBI 9.2. There is a newer version, 9.5 available for all architectures (amd64, arm64, ppc64le, s390x). The Dockerfiles should change to FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5
Additionally, some work should be done to see if we can support ubi-micro instead of ubi-minimal to reduce the threat surface attack area.
The Exchange uses registry.access.redhat.com/ubi9-minimal:latest as its base image. The packages are always up to date at the time of creating a container. The addition size shrinkage from going to the micro variant is moot presently for the mgmt hub, but this may be useful for storage constrained IoT devices in the field running an agent(Anax). Alternatively, project Ocre (https://lf-edge.atlassian.net/wiki/spaces/LE/pages/15832446/Project+Ocre) achieves this goal of space constrained devices better.
Is your feature request related to a problem? Please describe.
We should update all container images to UBI 9.5 to pull in security fixes and other updates.
Describe the solution you'd like.
Currently we are using UBI 9.2. There is a newer version, 9.5 available for all architectures (amd64, arm64, ppc64le, s390x). The Dockerfiles should change to FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5
Additionally, some work should be done to see if we can support ubi-micro instead of ubi-minimal to reduce the threat surface attack area.
relates to #3852
Describe alternatives you've considered
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: