Red Hat Bugzilla – Bug 1230930
Can't create external registries from API or CLI
Last modified: 2016-07-27 05:16:02 EDT
Description of problem: It is not available API or CLI for creating external registries Version-Release number of selected component (if applicable): S8C1 How reproducible: Aways Steps to Reproduce: 1. Check for API or CLI entry in the API docs or hammer docker help respectively 2. 3. Actual results: No API or CLI available for external registries Expected results: API and CLI should be available for external registries Additional info:
Can I get some draft text for a release note for this? I'm not fluent with the use of docker, containers, and external registries, so prefer that someone close to the topic put something together first. thanks a lot.
Docker images are stored on servers called registries. Satellite 6 have the ability to inspect not only the official docker registry (registry.hub.docker.com) but to inspect custom registries (information about how to create a private custom registry can be found here https://access.redhat.com/articles/881893#private). In the current state, the ability to add a custom registry is only available though the UI but not using hammer (CLI) or the API. With that said, user are recommended to use the UI to create an External Registry and point to an registry other than the official one. This is used when creating containers using the tab "External Registry" in order to search for a desired image and selecting a tag. This way the user can make Satellite pull the image from the custom registry and create the container. Let me know if you need more information.
We need to pull in the newest hammer_cli_foreman_docker. Released 0.0.4 upstream and opened a pull request against foreman-packaging here: https://github.com/theforeman/foreman-packaging/pull/1062
Unfortunately, this won't be testable until this bug is ON_QA: https://bugzilla.redhat.com/show_bug.cgi?id=1320338
Unfortunately, this is still not testable due to another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1230710 # hammer docker registry create --name docker.io --url https://registry-1.docker.io/ Could not create the registry: Unable to log in to this Docker Registry - Expected([200, 201, 202, 203, 204, 304]) <=> Actual(503 Service Unavailable) (Same error as reported in #1230710)
VERIFIED. @Sat6.2.0-Beta-Snap8 tfm-rubygem-hammer_cli_foreman_docker-0.0.4-1.el7sat.noarch # hammer docker registry create --name access.redhat.com --url https://registry.access.redhat.com Docker registry created # hammer docker registry list ---|-------------------|----------------------------------- ID | NAME | URL ---|-------------------|----------------------------------- 2 | access.redhat.com | https://registry.access.redhat.com ---|-------------------|----------------------------------- ... >>> hammer docker registry {create,info,update,delete,list} commands are available and work as expected >>> As hammer CLI relies on API calls, by testing hammer we also tested API
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-2016:1501