Docker: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342019-01-17T02:22:48ZForeman
Redmine Bug #25874 (Closed): hammer docker manifest list never shows docker tag nameshttps://projects.theforeman.org/issues/258742019-01-17T02:22:48ZPartha Ajipaji@redhat.com
<p>`hammer docker manifest list` has "Tag name" column, but never shows anything in it.</p>
<p>It seems that hammer_cli_foreman_docker/lib/hammer_cli_foreman_docker/docker_manifest.rb file expects tag field with definition of single tag. Meanwhile, API returns "tags" field with array of tags data.</p>
<p>git log on katello/app/models/katello/docker_manifest.rb shows that model used to have `has_one :docker_tag`, but that was changed to `has_many` in late 2016. Marking as Regression since I assume it did work as advertised before that change.</p> Bug #12020 (Closed): hammer container list does not show the idhttps://projects.theforeman.org/issues/120202015-09-30T16:02:41ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1230915">https://bugzilla.redhat.com/show_bug.cgi?id=1230915</a> <br /> Description of problem:<br />hammer docker container list does not show the id information for the container</p>
<p>Version-Release number of selected component (if applicable):<br />S8C1</p>
<p>How reproducible:<br />Aways</p>
<p>Steps to Reproduce:<br />1. hammer container list</p>
<p>Actual results:<br />ID information is not present</p>
<p>Expected results:<br />ID information is present</p>
<p>Additional info:</p>
<p>hammer> docker container list<br />------------|---------------------------------------------------------------------|---------|---------|------------------------------<br />NAME | IMAGE REPOSITORY | TAG | COMMAND | COMPUTE RESOURCE<br />------------|---------------------------------------------------------------------|---------|---------|------------------------------<br />centos-1 | default_organization-dockerproduct-centos | 7 | top | InternalDockerComputeResource<br />ubuntu-1 | ubuntu | 14.04.2 | top | InternalDockerComputeResource<br />wordpress-1 | wordpress | 4.2 | top | InternalDockerComputeResource<br />test-1 | default_organization-library-dockercontentview-dockerproduct-centos | latest | top | InternalDockerComputeResource<br />busybox-cv | default_organization-dev-dockercontentview-dockerproduct-busybox | latest | top | InternalDockerComputeResource<br />------------|---------------------------------------------------------------------|---------|---------|------------------------------</p> Feature #11672 (Closed): GET /docker/api/v2/registries/:id should return the username fieldhttps://projects.theforeman.org/issues/116722015-09-02T16:37:27ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1259513">https://bugzilla.redhat.com/show_bug.cgi?id=1259513</a> <br /> Description of problem:</p>
<p>When you create a new docker registry, you can optionally provide a username and password. However, our API does not seem to return either of them (see further down for an example of the output generated when using hammer).</p>
<p>Version-Release number of selected component (if applicable):</p>
<ul>
<li>Sat6.1.2-SNAP1</li>
</ul>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br />1. User either hammer cli to fetch information for a docker registry OR access /docker/api/v2/registries/:id directly<br />2.<br />3.</p>
<p>Actual results:</p>
<p>Notice how username and password are not returned</p>
<p>Expected results:</p>
<p>At least the username should be returned by the API call</p>
<p>Additional info:</p>
<p>hammer> docker registry update --id 2 --username='omaciel'<br />Docker registry updated<br />hammer> docker registry info --id 2<br />ID: 2<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 19:28:33<br />Updated at: 2015/09/02 20:24:51</p>
<p>hammer> exit<br />[root@ibm-x3250m4-05 ~]# hammer -u admin -p changeme -d docker registry info --id 2<br />[ INFO 2015-09-02 16:25:06 Init] Initialization of Hammer CLI (0.1.4.12) has started...<br />[DEBUG 2015-09-02 16:25:06 Init] Running at ruby 2.0.0-p598<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli_config.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_bootdisk.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_discovery.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_docker.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/gutterball.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/import.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/katello.yml has been loaded<br />[DEBUG 2015-09-02 16:25:06 Connection] Registered: foreman<br />[DEBUG 2015-09-02 16:25:06 API] Global headers: {<br /> :content_type => "application/json",<br /> :accept => "application/json;version=2",<br /> "Accept-Language" => "en" <br />}<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman (0.1.4.14) loaded<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman_bootdisk (0.1.2.7) loaded<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman_discovery (0.0.1.10) loaded<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] subcommand organization (HammerCLIForeman::Organization) was removed.<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] subcommand organization (HammerCLIKatello::Organization) was created.<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_gutterball (0.0.1.3) loaded<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_import (0.10.20) loaded<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_katello (0.0.7.17) loaded<br />[DEBUG 2015-09-02 16:25:07 Init] Using locale 'en'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli' loaded from '/usr/share/gems/gems/hammer_cli-0.1.4.12/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli@system' loaded from '/usr/share/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-foreman' loaded from '/usr/share/gems/gems/hammer_cli_foreman-0.1.4.14/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-foreman@system' loaded from '/usr/share/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer_cli_foreman_docker' loaded from '/usr/share/gems/gems/hammer_cli_foreman_docker-0.0.3.9/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-katello' loaded from '/usr/share/gems/gems/hammer_cli_katello-0.0.7.17/locale'<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] Called with options: {"option_debug"=>true, "option_username"=>"admin", "option_password"=>"***"}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerCommand] Called with options: {}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerRegistryCommand] Called with options: {}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerRegistryCommand::InfoCommand] Called with options: {"option_id"=>"2"}<br />[ INFO 2015-09-02 16:25:07 API] GET /docker/api/v2/registries/2<br />[DEBUG 2015-09-02 16:25:07 API] Params: {}<br />[DEBUG 2015-09-02 16:25:07 API] Headers: {<br /> :params => {}<br />}<br />[DEBUG 2015-09-02 16:25:07 API] Response: {<br /> "id" => 2,<br /> "name" => "Red Hat Docker Registry",<br /> "url" => "https://registry.access.redhat.com",<br /> "description" => nil,<br /> "created_at" => "2015-09-02T19:28:33Z",<br /> "updated_at" => "2015-09-02T20:24:51Z",<br /> "locations" => [],<br /> "organizations" => []<br />}<br />[DEBUG 2015-09-02 16:25:07 API] Response headers: {<br /> :date => "Wed, 02 Sep 2015 20:25:07 GMT",<br /> :server => "Apache/2.4.6 (Red Hat Enterprise Linux)",<br /> :foreman_version => "1.7.2",<br /> :foreman_api_version => "2",<br /> :x_ua_compatible => "IE=Edge,chrome=1",<br /> :cache_control => "must-revalidate, private, max-age=0",<br /> :x_request_id => "a0fedd63901dfcfed505917ca8ef51bb",<br /> :x_runtime => "0.054340",<br /> :x_rack_cache => "miss",<br /> :x_powered_by => "Phusion Passenger 4.0.18",<br /> :set_cookie => [<br /> [0] "_session_id=BAh7B0kiD3Nlc3Npb25faWQGOgZFRkkiJWNkOTU0ZTRjYjU4ODMyYThjOTc2NmRiMWQwM2M4OWUwBjsAVEkiC2xvY2FsZQY7AEYiB2Vu--67efdbc1c468785e0e4945ace6a6a83ba3907dab; path=/; secure; HttpOnly" <br /> ],<br /> :etag => "\"71f8a3f3f2b750eab907421469b85345\"",<br /> :status => "200 OK",<br /> :transfer_encoding => "chunked",<br /> :content_type => "application/json; charset=utf-8" <br />}<br />ID: 2<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 19:28:33<br />Updated at: 2015/09/02 20:24:51</p> Bug #11671 (Closed): docker registry command does not provide IDshttps://projects.theforeman.org/issues/116712015-09-02T15:46:53ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1259498">https://bugzilla.redhat.com/show_bug.cgi?id=1259498</a> <br /> Description of problem:</p>
<p>The new 'docker registry' command has several subcommands that can use the ID for a registry to perform several CRUD actions but the ID is never displayed by 'docker registry list' or 'docker registry info'. Furthermore, the following fields are also never displayed: description, username, password</p>
<p>See the output of using hammer registry below:</p>
<p>hammer> docker registry<br />Usage:<br /> docker registry [OPTIONS] SUBCOMMAND [ARG] ...</p>
<p>Parameters:<br /> SUBCOMMAND subcommand<br /> [ARG] ... subcommand arguments</p>
<p>Subcommands:<br /> create Create a docker registry<br /> delete Delete a docker registry<br /> info Show a docker registry<br /> list List all docker registries<br /> update Update a docker registry</p>
<p>Options:<br /> <del>h, --help print help<br />hammer> docker registry create<br />Could not create the registry:<br /> Missing arguments for 'name', 'url'<br />hammer> docker registry create --name="Red Hat Docker Registry" --url="https://registry.access.redhat.com" <br />Docker registry created<br />hammer> docker registry list<br />-----------------------</del>|-----------------------------------<br />NAME | URL<br />------------------------|-----------------------------------<br />Red Hat Docker Registry | <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />------------------------|-----------------------------------<br />hammer> docker registry info -h<br />Usage:<br /> docker registry info [OPTIONS]</p>
<p>Options:<br /> --id ID<br /> --name NAME Name to search by<br /> -h, --help print help<br />hammer> docker registry info --name='Red Hat Docker Registry'<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 18:44:24<br />Updated at: 2015/09/02 18:44:24</p>
<p>hammer> docker registry update -h<br />Usage:<br /> docker registry update [OPTIONS]</p>
<p>Options:<br /> --description DESCRIPTION<br /> --id ID<br /> --name NAME Name to search by<br /> --new-name NEW_NAME<br /> --password PASSWORD<br /> --url URL<br /> --username USERNAME<br /> -h, --help print help<br />hammer> docker registry update --name='Red Hat Docker Registry' --description='Updated this field'<br />Docker registry updated<br />hammer> docker registry info --name='Red Hat Docker Registry'<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 18:44:24<br />Updated at: 2015/09/02 18:47:19</p>
<p>hammer> docker registry update --name='Red Hat Docker Registry' --username='Updated this field'<br />Docker registry updated<br />hammer> docker registry info --name='Red Hat Docker Registry'<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 18:44:24<br />Updated at: 2015/09/02 18:47:46</p>
<p>hammer> docker registry update --name='Red Hat Docker Registry' --url='http://localhost'<br />Docker registry updated<br />hammer> docker registry info --name='Red Hat Docker Registry'<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="http://localhost">http://localhost</a><br />Created at: 2015/09/02 18:44:24<br />Updated at: 2015/09/02 18:48:15</p>
<p>hammer> docker registry update --name='Red Hat Docker Registry' --new-name='RH'<br />Docker registry updated<br />hammer> docker registry info --name='Red Hat Docker Registry'<br />Error: registry not found<br />hammer> docker registry info --name='RH'<br />Name: RH<br />URL: <a class="external" href="http://localhost">http://localhost</a><br />Created at: 2015/09/02 18:44:24<br />Updated at: 2015/09/02 18:48:46</p>
<p>hammer> docker registry delete -h<br />Usage:<br /> docker registry delete [OPTIONS]</p>
<p>Options:<br /> --id ID<br /> --name NAME Name to search by<br /> <del>h, --help print help<br />hammer> docker registry delete --name='RH'<br />Docker registry deleted<br />hammer> docker registry list<br />----</del>|----<br />NAME | URL<br />-----|----<br />hammer> docker registry info --name='RH'<br />Error: registry not found</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>This is Sat6.1.2-SNAP1</p>
<ul>
<li>docker-1.7.1-108.el7.x86_64</li>
<li>docker-selinux-1.7.1-108.el7.x86_64</li>
<li>pulp-docker-plugins-0.2.5-1.el7sat.noarch</li>
<li>python-pulp-docker-common-0.2.5-1.el7sat.noarch</li>
<li>ruby193-rubygem-docker-api-1.17.0-1.1.el7sat.noarch</li>
<li>ruby193-rubygem-foreman_docker-1.2.0.20-1.el7sat.noarch</li>
<li>rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch</li>
</ul>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br />1. Use the 'docker registry' command to create a new registry and then attempt to use any of its subcommand and pass the ID (i.e. --id) argument to perform any actions against the registry<br />2.<br />3.</p>
<p>Actual results:</p>
<p>The ID is never displayed by hammer and therefore one cannot use --id with its subcommands</p>
<p>Expected results:</p>
<p>Additional info:</p> Bug #11354 (Closed): Can't set container options if target daemon is docker 1.7.1https://projects.theforeman.org/issues/113542015-08-14T11:20:35ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1253422">https://bugzilla.redhat.com/show_bug.cgi?id=1253422</a> <br /> Description of problem:<br />Unable to set container options if docker daemon package version is 1.7.1.</p>
<p>Version-Release number of selected component (if applicable):<br />Satellite 6.1.1 (CDN)</p>
<p>How reproducible:<br />Aways</p>
<p>Steps to Reproduce:<br />1. Create a new container using the container wizard (don't matter if getting the image from content view or Docker HUB)<br />2. Set the CPU, CPU share and memory<br />3. Try to finish the wizard</p>
<p>Actual results:</p>
<p>Expected results:</p>
<p>Additional info:<br />Manually applied [1]in order to make container creation work, but for the memory and other options another fix is required.</p>
<p>[1] <a class="external" href="https://github.com/theforeman/foreman-docker/commit/e88059db3a33445f654b199d803e4364662b7eaf#diff-8f6cf17bcdab083ba9adc56132c35f1aR11">https://github.com/theforeman/foreman-docker/commit/e88059db3a33445f654b199d803e4364662b7eaf#diff-8f6cf17bcdab083ba9adc56132c35f1aR11</a></p> Bug #10404 (Closed): Bad URI error message when creating Docker container from Docker Hub pagehttps://projects.theforeman.org/issues/104042015-05-06T19:29:09ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1209639">https://bugzilla.redhat.com/show_bug.cgi?id=1209639</a> <br /> Description of problem:</p>
<p>Trying to create a new Docker container using the Docker Hub form is now failing with a bad URI error (see attached screenshot).</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br />1. Create a new Docker container<br />2. Select the proper compute resource<br />3. Select the Docker Hub form<br />4. Type 'wordpress' and then click the 'search' button (ie. magnifying glass button)</p>
<p>Actual results:</p>
<p>The screenshot shows an error message. Also, the message says to use the "Foreman ticketing system" instead of Red Hat Bugzilla.</p>
<p>Expected results:</p>
<p>Additional info:</p> Bug #9901 (Closed): Provisioning the same container name twice from the CLI in foreman just gives...https://projects.theforeman.org/issues/99012015-03-25T15:01:46ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1204298">https://bugzilla.redhat.com/show_bug.cgi?id=1204298</a> <br /> Would be nice to show an error like "Container name already taken".</p>
<blockquote>
<p>hammer -u admin -p changeme docker container create --name hello --command bash \</p>
</blockquote>
--repository-name busybox --tag latest --compute-resource DockerCP<br />Docker Container Created
<blockquote>
<p>hammer -u admin -p changeme docker container create --name hello --command bash \</p>
</blockquote>
--repository-name busybox --tag latest --compute-resource DockerCP<br />Could not create the container:<br /> Error: 500 Internal Server Error Bug #9570 (Closed): Can't connect to docker compute resource (Docker::Error::AuthenticationError)https://projects.theforeman.org/issues/95702015-02-26T14:55:20ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1196777">https://bugzilla.redhat.com/show_bug.cgi?id=1196777</a> <br /> Description of problem:</p>
<p>I think this might be due to some packages on RHEL6 or something. Not sure.</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>Nightly build. Here's the docker-related packages:</p>
<p>pulp-docker-plugins-0.2.2-1.el6.noarch<br />ruby193-rubygem-foreman_docker-1.2.0-1.fm1_8.el6.noarch<br />python-pulp-docker-common-0.2.2-1.el6.noarch<br />ruby193-rubygem-docker-api-1.17.0-1.el6.noarch<br />docker-io-1.4.1-3.el6.x86_64</p>
<p>How reproducible:</p>
<p>Always.</p>
<p>Steps to Reproduce:<br />1. Set up the nightly build on RHEL6 with these options in /etc/sysconfig/docker:</p>
<p>other_args='--selinux-enabled=true --host tcp://0.0.0.0:2375 --host unix:///var/run/docker.sock'<br />DOCKER_CERT_PATH=/etc/docker</p>
<p>2. Create a compute resource<br />3. Click on Test Connection</p>
<p>Actual results:</p>
<p>Docker::Error::AuthenticationError</p>
<p>Docker log:</p>
<p>ERRO<sup><a href="#fn0014">0014</a></sup> Handler for POST /auth returned error: Registration: "Missing username field" <br />ERRO<sup><a href="#fn0014">0014</a></sup> HTTP Error: statusCode=500 Registration: "Missing username field"</p>
<p>Expected results:</p>
<p>Success</p>
<p>Additional info:</p> Bug #9382 (Closed): Wrong Docker Compute resource getting provisionedhttps://projects.theforeman.org/issues/93822015-02-13T15:41:47ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1192614">https://bugzilla.redhat.com/show_bug.cgi?id=1192614</a> <br /> 1) Have 2 compute resources of Type docker, preferably one with a bad url(BadHost) and one good container host url (GoodHost)<br />2) Goto Containers <del>> new container -> select BadHost and then go to "Docker Hub" for images<br />3) Search for busybox repo ( you should get a 500 but thats a different bug).<br />4) Now do Containers -> new container again</del> > but select the good host<br />5) Select katello-registry under images and select a katello repo and tag<br />6) Go ahead and try to create a new container hitting next and submit</p>
<p>Note that the container getting provisioned on the bad host, even though you asked it to get created on the Good One,</p> Bug #9365 (New): Compute resources with bad connections should be selectable in New Containers pagehttps://projects.theforeman.org/issues/93652015-02-12T17:21:29ZPartha Ajipaji@redhat.com
<p>Compute resources or Docker Hosts with bad connection information like url/username passwords should NOT be selectable in the new containers page.</p> Bug #9341 (Closed): Need to require higher verison of docker apihttps://projects.theforeman.org/issues/93412015-02-11T14:59:25ZPartha Ajipaji@redhat.com
<p>The foreman docker code seems to be written with the assumption that its talking to docker-api > 1.16</p>
<p>Need to update the gemspec.</p> Bug #9311 (Closed): New Container katello tab needs to be renamed to Local/Local Contenthttps://projects.theforeman.org/issues/93112015-02-10T11:08:30ZPartha Ajipaji@redhat.com
<p>Have katello plugin installed. <br />1) Go to new container<br />2) Select a docker host<br />3) Notice the Katello tab shows up.</p>
<p>As a katello/satellite user you are going to be provisioning images that you synced locally/uploaded to a locally published repo.</p>
<p>So the tab needs a more approiate name than "Katello" <br />Some of the suggestions are</p>
<p>Local, <br />Local Registries,<br />Local Content, <br />Synced Content,<br />Published Content,<br />Hosted Content<br />Published Registries<br />Hosted Registries<br />Content View Registries,<br /> Content View, <br />Synced,</p>
<p>Need to pick one and rename Katello to that,</p> Bug #9229 (Closed): Not handling private registries with no username or password correctlyhttps://projects.theforeman.org/issues/92292015-02-04T20:14:39ZPartha Ajipaji@redhat.com
<p>1) Set up a private registry that does not accept username/password (no auth) with some images.<br />2) Go to new containers page<br />3) Select "external registry" and in there select the one you setup.<br />4) Type name of an image in that registry and hit search.</p>
<p>Notice you get an ise in the server saying username/password did not match.</p> Bug #8873 (Feedback): need to handle non standalone registry auth for a docker pull callhttps://projects.theforeman.org/issues/88732015-01-08T10:56:48ZPartha Ajipaji@redhat.com
<p>PR <a class="external" href="https://github.com/theforeman/foreman-docker/pull/65">https://github.com/theforeman/foreman-docker/pull/65</a> addresses the docker pull call for the standalone registries. <br />But we need to address cases involving non standalone registries, where we need to query the index for the location of the image, we also must use the authentication token that the index passes to us together with the response.<br />look at <br /><a class="external" href="https://docs.docker.com/reference/api/hub_registry_spec/#pull">https://docs.docker.com/reference/api/hub_registry_spec/#pull</a></p>
<p>for more info</p> Bug #8772 (Rejected): New container External Registry not working after model updatehttps://projects.theforeman.org/issues/87722014-12-19T19:05:30ZPartha Ajipaji@redhat.com
<p>1) New Container<br />2) Select external registry <br />3) Search on an image tag.</p>
<p>The search goes to docker hub instead of registry.</p>
<p><a class="external" href="https://github.com/theforeman/foreman-docker/commit/c57dae5641a637761fb51058ad2607c3a9db8ce1">https://github.com/theforeman/foreman-docker/commit/c57dae5641a637761fb51058ad2607c3a9db8ce1</a> had a couple of typos making this not work,</p>