-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
sat-artemis
-
None
-
None
-
None
-
No Coverage
Description of problem:
Information is not clear about considerations/requirements when pushing Docker content to Satellite
How reproducible:
100%
Is this issue a regression from an earlier version:
Steps to Reproduce:
1. Checking the docs, we can see the message below
The pushed container registry name must contain only lowercase characters.
2.
3.
Actual behavior:
My understanding is that the "container registry name" is related to the registry name only, and not the whole container string, right?
# podman search wallsat616-rhel8.d.sysmgmt.cee.redhat.com/ NAME DESCRIPTION wallsat616-rhel8.d.sysmgmt.cee.redhat.com/acme-container_stuff-ubi8_httpd-24
Above, we can see the string
wallsat616-rhel8.d.sysmgmt.cee.redhat.com/acme-container_stuff-ubi8_httpd-24
About the statement "pushed container registry name must contain only lowercase characters", this refer to "wallsat616-rhel8.d.sysmgmt.cee.redhat.com/acme-container_stuff-ubi8_httpd-24" or "wallsat616-rhel8.d.sysmgmt.cee.redhat.com"
Based on this doc [1], the registry name should be only the server FQDN
For example, the registry.redhat.io/ubi8/ubi container image is identified by:
- Registry server (registry.redhat.io)
- Namespace (ubi8)
- Image name (ubi)
Expected behavior:
Accurate information in our docs
Business Impact / Additional info:
This is causing some issues, in the same document, we can see the information below
podman push My_Container_Image_Hash satellite.example.com/My_Organization_Label/My_Product_Label/My_Repository_Name[:_My_Tag_] podman push My_Container_Image_Hash satellite.example.com/id/My_Organization_ID/My_Product_ID/My_Repository_Name[:_My_Tag_]
Above, we can see the examples with the capital letter "My_Product_Label", for instance, and assuming that my label on Satellite is something as Container, this will not work, once the complete URL "registry + namespace + image" has to be in lowercase.