Red Hat Bugzilla – Bug 1263464
[DOCS] Clarify steps required to push images to internal docker registry
Last modified: 2018-05-08 20:30:36 EDT
Document URL: https://docs.openshift.com/enterprise/3.0/using_images/docker_images/overview.html
Section Number and Name: pushing to internal docker registry needs project namespace.
Describe the issue:
- Out line what is needed when pushing images manually to internal registry
- For example project namespace is needed to be added when doing a docker push.
# docker tag <image> <docker-registry-ip>:5000/<Project_Name>/<image>
Suggestions for improvement:
- Add a section that outlines how to work with our registry
@ryan I *appears* that this BZ is requesting that we add the namespace to the docker push and docker tag commands in our docs. Can you clarify?
If so, have we addressed this concern via https://github.com/openshift/openshift-docs/commit/4b8377d67ce2968ffe4c5f5bb9f9f24e2b84e59e#diff-d7dbe137f42b2f8f406596161a89db90
This commit was a few days after you created this BZ.
The docs now have:
16. Validate the docker client connection. Running docker push to the registry or docker pull from the registry should succeed. Make sure you have logged into the registry.
$ docker tag|push <registry/image> <internal_registry/project/image>
$ docker pull busybox
$ docker tag docker.io/busybox 172.30.124.220:5000/openshift/busybox
$ docker push 172.30.124.220:5000/openshift/busybox
cf2616975b4a: Image successfully pushed
This can be closed, docs now satisfy