Bug #8637
cannot pull/create containers from local registry (multi registry not working)
Description
1) Install a local registry (I yum docker-registry, make sure you enable search and run it on 5050 for this example)
2) Tag a custom image that you ve already pulled before
docker tag fedora/ssh localhost:5050/myfedssh
3) Next push it to your local registry
docker push localhost:5050/myfedssh
4) Now login to Katello -> Containers -> Registries -> New Registry
5) Add one and point to localhost:5050
6) Go to the new container page, assuming you have a docker compute resource, Select and continue
7) Select external registry -> and select the one you created.
8) Now search for the myfedssh .. Assuming it found that select the "latest" tag
9) Continue on the next couple of screens and hit submit
Error creating container. Check the Foreman logs: Expected([200, 201, 202, 203, 204, 304]) <=> Actual(404 Not Found)
Fog error: Expected([200, 201, 202, 203, 204, 304]) <=> Actual(404 Not Found)
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/docker-api-1.15.0/lib/docker/connection.rb:59:in `block (2 levels) in <class:Connection>'
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/docker-api-1.15.0/lib/docker/container.rb:181:in `create'
/home/paji/centos/projects/foreman-docker/app/models/foreman_docker/docker.rb:74:in `create_container'
/home/paji/centos/projects/foreman-docker/app/controllers/containers/steps_controller.rb:70:in `start_container'
/home/paji/centos/projects/foreman-docker/app/controllers/containers/steps_controller.rb:31:in `update'
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/actionpack-3.2.21/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/actionpack-3.2.21/lib/abstract_controller/base.rb:167:in `process_action'
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/actionpack-3.2.21/lib/action_controller/metal/rendering.rb:10:in `process_action'
/home/paji/.rvm/gems/ruby-2.0.0-p598/gems/actionpack-3.2.21/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/home
Related issues
Associated revisions
Fixes #8637 - local registry container support
Prior to this commit, one could not start containers connected to a
local or non docker hub external registry. This is because the container
parametrize call did not properly prefix the registry url in its Image name.
This commit fixes that.
History
#1
Updated by Partha Aji over 8 years ago
- Blocks Tracker #7125: Docker Content Support added
#2
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-docker/pull/57 added
- Pull request deleted (
)
#3
Updated by Partha Aji about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-docker|555e836d32eecf4d1ac4214ae27b4015469c995b.
Fixes #8637 - local registry container support
Prior to this commit, one could not start containers connected to a
local or non docker hub external registry. This is because the container
parametrize call did not properly prefix the registry url in its Image name.
This commit fixes that.