Cannot pull 10.0 tag

[AThomsen]

failed to resolve reference "registry.access.redhat.com/ubi9/dotnet-100-runtime:10.0": registry.access.redhat.com/ubi9/dotnet-100-runtime:10.0: not found

and

failed to resolve reference "registry.access.redhat.com/ubi9/dotnet-100-runtime:10.0.0": registry.access.redhat.com/ubi9/dotnet-100-runtime:10.0.0: not found

registry.access.redhat.com/ubi9/dotnet-100-runtime (latest) works though!

[omajid]

This was an intentional change to make .NET container images match the other container images published in the UBI context.

Since registry.access.redhat.com/ubi9/dotnet-100-runtime can only mean the .NET 10 runtime, we thought the 10.0 tag, duplicating the .NET version, wasn't adding any extra value/information. We prefer simply using registry.access.redhat.com/ubi9/dotnet-100-runtime:latest.

Worse, there is a conflict with existing tags based on the RHEL version, which our build systems already add to the images. You can currently pull registry.access.redhat.com/ubi9/dotnet-100-runtime:9.7 which doesn't get you .NET 9, but .NET 10 based on RHEL/UBI 9.7. If we ever do a registry.access.redhat.com/ubi10/dotnet-100-runtime, the 10.0 tag will get you something based on RHEL/UBI 10.0, and not the latest .NET 10.0 version.

cc @tmds

[tmds]

Yes, the change is intentional for consistency with other UBI repos. See 2nd item in https://docs.redhat.com/en/documentation/net/10.0/html/release_notes_for_.net_10.0_containers/known-issues-for-containers.

We are providing the .NET UBI images also through additional repos now which do use .NET versions for tags. https://developers.redhat.com/articles/2025/12/01/what-you-need-know-about-red-hats-net-container-images#_net_images gives an overview.

[AThomsen]

@omajid , @tmds ok. You might want to fix this:

Also, the pull example commands for podman and docker on https://catalog.redhat.com/en/software/containers/ubi9/dotnet-100-runtime/68c12d7464c1f89e50bc34db#get-this-image mentions
podman pull registry.access.redhat.com/ubi9/dotnet-100-runtime:10.0.0

[tmds]

@AThomsen thanks for reporting. I'll look into this.

[tmds]

@AThomsen the bug that caused the erroneous tags to appear in the catalog has been fixed.