<div dir="ltr">Hi Miquel,<div><br></div><div>Thanks for the information. Well, I am gonna try pushing Portus on the same machine with the registry. ...as in best practice.</div><div><br></div><div>Cheers,</div><div>Ali</div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 29, 2016 at 3:37 PM, Miquel Sabaté Solà <span dir="ltr"><<a href="mailto:msabate@suse.com" target="_blank">msabate@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font face="Noto Sans">Hello,</font><div><div class="h5"><br>
<br>
<div>On 01/29/2016 12:09 AM, Ali Ok wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>We have a private Docker registry in a remote machine used
by multiple developers.</div>
<div>Say, for some political reason, we cannot install Portus
anywhere except</div>
<div><br>
</div>
<div>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: <a href="https://github.com/atc-/docker-registry-ui" target="_blank">docker-registry-ui</a></div>
<div><br>
</div>
<div>What do you think about this idea?<br>
</div>
<div><br>
</div>
<div>Anyway, I was hoping to have this in 3 easy steps:</div>
<div><br>
</div>
<div>1. <font face="monospace, monospace">docker run
portus/some-portus-image-with-no-bundled-registry -d -p
1234:5678 /some/host/dir:/portus/data/folder</font></div>
<div>2. Open localhost:xxxx</div>
<div>3. Enter details of the registry</div>
<div>--> There you go.</div>
<div><br>
</div>
<div>Of course I made up all of steps above. But you get the
idea I hope.</div>
<div>Is something like this already possible?<br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Ali</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Containers mailing list
<a href="mailto:Containers@lists.suse.com" target="_blank">Containers@lists.suse.com</a>
<a href="http://lists.suse.com/mailman/listinfo/containers" target="_blank">http://lists.suse.com/mailman/listinfo/containers</a>
</pre>
</blockquote>
<br>
In principle it might look like it's possible, but it's not as far
as I know.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Greetings,<br>
Miquel<br>
</div>
<br>_______________________________________________<br>
Containers mailing list<br>
<a href="mailto:Containers@lists.suse.com">Containers@lists.suse.com</a><br>
<a href="http://lists.suse.com/mailman/listinfo/containers" rel="noreferrer" target="_blank">http://lists.suse.com/mailman/listinfo/containers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">My Blog: <a href="http://blog.aliok.com.tr/" target="_blank">http://blog.aliok.com.tr</a><br>Twitter: <a href="http://twitter.com/aliok_tr" target="_blank">http://twitter.com/aliok_tr</a>
</div>
</div></div></div>