Documentation: local registry not configured to pull from docker hub

Bug #1647436 reported by Matt McEuen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Low
Matt McEuen

Bug Description

When created per the "Multinode Deployment of Kolla" instructions, a local registry is not configured to proxy the official builds hosted in Docker Hub, resulting in a failure of "kolla-ansible pull".

The Multinode instructions direct you to use the start-registry command (https://github.com/openstack/kolla/blob/master/tools/start-registry), which works fine when you build/populate your own images.

Perhaps start-registry should be augmented to include a "-e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io" parameter? In my case that successfully sets up my registry to pull (and cache) from Docker Hub.

Tags: doc
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

If u wanna use the image in docker.io, you want need create a docker registry locally. Just configure the globals.yml file to use the docker.io directly.

Changed in kolla:
status: New → Won't Fix
Revision history for this message
Matt McEuen (mm9745) wrote :

Thanks, Jeffrey, that makes sense! However, it's not what the Multinode Deployment of Kolla guide says -- it says "A local registry is required for a multinode Kolla deployment".

I think the Multinode doc needs to say one of two things:

1) Local registry is required, but you configure it to proxy Docker Hub

2) Local registry is not required -- use it if you want to build your own images; otherwise configure docker.io in globals.yml

I'm happy to help with the doc update (or updating the start-registry script if appropriate), if you can help me understand the desired behavior.

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

Matt

cool. please add this into the doc. ;)

Changed in kolla:
status: Won't Fix → Triaged
tags: added: doc
Matt McEuen (mm9745)
Changed in kolla:
assignee: nobody → Matt McEuen (mm9745)
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
importance: Undecided → Low
summary: - Local registry not configured to pull from docker hub
+ Documentation: local registry not configured to pull from docker hub
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/413806

Changed in kolla:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/413806
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=19b0defb9220ff55e16f857dd6741b7e16a44bc7
Submitter: Jenkins
Branch: master

commit 19b0defb9220ff55e16f857dd6741b7e16a44bc7
Author: Matt McEuen <email address hidden>
Date: Wed Dec 21 17:18:07 2016 -0600

    Configure local registries to proxy docker hub

    Added the REGISTRY_PROXY_REMOTEURL parameter to the registry
    creation script, so that the registry will mirror images from
    Docker Hub (while still being able to host custom-built images).
    Updated the Multinode guide to reflect this.

    Change-Id: Ib789241fd2947b06fb0dc5732a0bf28431e1403d
    Closes-Bug: #1647436

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 4.0.0.0b3

This issue was fixed in the openstack/kolla 4.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.