1. Proposed title of this feature request Support for more slashes in image tag names 3. What is the nature and description of the request? When attempting to push an image with more slash-separated segments than the standard <docker registry ip or route>[:<port>]/<namespace>/<imagename>, it fails out with an error (as currently expected with the specifications for the docker push): error: can't build "http://example.net/myproject/myapp.git": can't build "exampleregistry.net/project/subheading/image:tag": the docker pull spec "exampleregistry.net/project/subheading/image:tag" must be two or three segments separated by slashes 5. How would the customer like to achieve this? (List the functional requirements here) Be able to tag and push to a subheading of a project. One possible way to do this would be to simply allow extra slashes but that are all part of the image name, or are otherwise simply subheadings (with the first one being the namespace and any extra "in-between" slashes just being metadata). 6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Run docker push on a name like exampleregistry.net/project/subheading/image:tag 7. Is there already an existing RFE upstream or in Red Hat bugzilla? Not that I could find
This also applies with pulls: oc new-build ssh://my.example.net:22/subDir/anotherDir/_git/StevenExample error: can't build "ssh://my.example.net:22/subDir/anotherDir/_git/StevenExample": can't build "docker-enterprise.example.net/imagedir/myimageproject/rhel/rhel7:2016": the docker pull spec "docker-enterprise.example.net/imagedir/myimageproject/rhel/rhel7:2016" must be two or three segments separated by slashes
https://github.com/openshift/source-to-image/pull/594 for s2i piece
At the origin (master) added support of multi-segment names. You can import images and/or build them. The docker-registry still doesn't support such names (and not planned). Please, verify.
QA ping?
(In reply to Alexey Gladkov from comment #10) > At the origin (master) added support of multi-segment names. You can import > images and/or build them. The docker-registry still doesn't support such > names (and not planned). > > Please, verify. Sorry, I would like to clarify your meaning; OpenShift can now support using images with more segments, but the registry cannot store them? I.E. OpenShift can now process "external" images with that name format but our registry will continue to adhere to the standard?
Openshift supports DockerReference with more segments. You can create an imagestream from the external docker registry and use it for builds, you can use multi-segment names in the build config. See https://bugzilla.redhat.com/show_bug.cgi?id=1386543 for more info.
Ok, thanks, that makes sense. I am verifying with customer if this satisfies.
Hi, Ok so as per comment 3 at https://bugzilla.redhat.com/show_bug.cgi?id=1386543#c3 we do not plan to support multi-segments in imagestream names, correct? All we will support is external images that have multi segments, but if they are imported as an IS they will take the 3-segment format? I would like to get final verification before passing this along to customer.
> we do not plan to support multi-segments in imagestream names, correct? Yes. > All we will support is external images that have multi segments, but if they are imported as an IS they will take the 3-segment format? The imagestream name will have just single segment, but the docker reference in the imagestream can have 3-segment format.
Confirmed with latest OCP3.4 , the feature has supportted: openshift v3.4.0.23+24b1a58 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 [root@zhouy testjson]# oc describe is ruby-22-centos7 Name: ruby-22-centos7 Namespace: zhouy2 Created: 4 minutes ago Labels: <none> Annotations: openshift.io/image.dockerRepositoryCheck=2016-11-08T09:40:02Z Docker Pull Spec: 172.30.196.46:5000/zhouy2/ruby-22-centos7 Unique Images: 1 Tags: 1 latest tagged from 073b6b6e.ngrok.io/test/centos/ruby-22-centos7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0066
https://www.caradaftarsbobetterbaru.com/