[Containers] portus integration with existing running docker v2.2 registry

Benjamin Fernandis benjo11111 at gmail.com
Thu Feb 11 16:17:21 MST 2016


I don't know where i m doing mistake, but if i add another registry which
is not using ssl and with same configuration in portus and in registry, it
works. I can see data in portus webpage.

but while adding ssl enabled registry facing problem.



On Fri, Feb 12, 2016 at 2:24 AM, Miquel Sabaté Solà <msabate at suse.com>
wrote:

> Hello Benjamin,
>
> On 02/11/2016 03:02 AM, Benjamin Fernandis wrote:
>
> Hi,
>
> we using docker v2.2 registry with ssl cert on centos 7 and it is working
> fine.
>
> we can push and pull from network without --insecure-registry flag.
>
> today, we deployed portus on opensuse vm and then added registry in
> webpage of portus.
>
> but we have not see any repositories or namespace data in portus web page.
> Even when tried to check in DB it shows empty.
>
>
> Right. I think that it's expected for Portus to automatically "import" the
> images from the registry you just configured. This is tricky mainly
> because: what if you have images contained inside of namespaces Portus
> knows nothing about ? which team should own these missing namespaces ? This
> is a question that we plan to fix as soon as possible, but we are still
> discussing the best way to do it.
>
> Now, you could say, well, at least import the images that are not
> contained in namespaces, right ? We can do this, but you have to use Crono.
> See more about Crono in our documentation [1]. Basically, it will
> periodically check for images available in the registry and not registered
> in Portus. Because of the aforementioned limitation with namespaces, Crono
> will only import images that are not contained in namespaces that are
> unknown to Portus. One way to work-around this limitation is to create the
> namespaces manually, and let Crono update the DB on the next iteration.
>
> That being said, there's a known bug in our code regarding the
> synchronization with crono (see [2]). This is fixed in both master and
> 2.0.3 (which will be released next week).
>
>
> there is no error in portus log and while checking in registry logs, i can
> see request comes from portus and i can see repositories data as per
> registry but nothing comes in portus web page.
>
> there is no error in reigstry log.
>
> i copied registry certificate to portus /etc/pki/trust/anchors folder.
>
> please suggest me if i m missing anything here.
>
> registry config.
>
> docker run \
>         -d  --restart=always --name registry \
>         -e REGISTRY_LOG_LEVEL=info \
>         -p 5000:5000 \
>         -e SEARCH_BACKEND=sqlalchemy \
>         -v `pwd`/certs:/certs \
>         -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/xyz.crt \
>         -e REGISTRY_HTTP_TLS_KEY=/certs/xyz.key \
>         -v /etc/localtime:/etc/localtime:ro \
>         -v /data/docker-v2:/var/lib/registry \
>          registry:2.2
>
>
> registry is running in container on centos 7.
> portus is running in opensuse vm.
>
> Thanks
> Ben
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>
>
> Hope this helps,
> Miquel
>
> [1]
> http://port.us.org/features/1_Synchronizing-the-Registry-and-Portus.html
> [2] https://github.com/SUSE/Portus/issues/720
>
> _______________________________________________
> Containers mailing list
> Containers at lists.suse.com
> http://lists.suse.com/mailman/listinfo/containers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160212/381f3636/attachment.htm>


More information about the Containers mailing list