[Containers] Using local Portus as a registry explorer/manager

[Ali Ok]

Hi Miquel,

Thanks for the information. Well, I am gonna try pushing Portus on the same
machine with the registry. ...as in best practice.

Cheers,
Ali

On Fri, Jan 29, 2016 at 3:37 PM, Miquel Sabaté Solà <msabate at suse.com>
wrote:

> Hello,
>
>
> On 01/29/2016 12:09 AM, Ali Ok wrote:
>
> Hi all,
>
> We have a private Docker registry in a remote machine used by multiple
> developers.
> Say, for some political reason, we cannot install Portus anywhere except
>
> I was wondering if installing Portus on developers' local machines and
> using it to manage that remote registry makes sense or not. Pretty much
> like this primitive tool: docker-registry-ui
> <https://github.com/atc-/docker-registry-ui>
>
> What do you think about this idea?
>
> Anyway, I was hoping to have this in 3 easy steps:
>
> 1. docker run portus/some-portus-image-with-no-bundled-registry -d -p
> 1234:5678 /some/host/dir:/portus/data/folder
> 2. Open localhost:xxxx
> 3. Enter details of the registry
> --> There you go.
>
> Of course I made up all of steps above. But you get the idea I hope.
> Is something like this already possible?
>
> Cheers,
> Ali
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>
>
> In principle it might look like it's possible, but it's not as far as I
> know.
>
> First of all, you have to change the configuration of the registry to
> point to your authorization service (Portus). I don't know if you are
> allowed to do that in your case :) Anyways, let's say that you are allowed
> to do that. The registry's configuration has to point to a single hostname
> in the "auth" section of the configuration. Therefore, you can only point
> to a specific Portus instance. This means that you cannot just install
> Portus into multiple machines, since the registry can only point to one of
> them. Therefore, the only way in which this is possible would be to install
> it in a host where all the developers have access to.
>
> Moreover, you'd have the same issue with the docker-registry-ui you're
> mentioning. It's just not possible as far as I know.
>
> Greetings,
> Miquel
>
> _______________________________________________
> Containers mailing list
> Containers at lists.suse.com
> http://lists.suse.com/mailman/listinfo/containers
>
>


-- 
My Blog: http://blog.aliok.com.tr
Twitter: http://twitter.com/aliok_tr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160129/a5930550/attachment.htm>