<div dir="ltr">Hi Miquel,<div><br></div><div>I deployed rpm version on opensuse and it is working fine.</div><div><br></div><div>Can you please guide me what is require to enable login in docker command line.</div><div><br></div><div>currently i tested portus integration with docker registry and ldap authentication to pourtus from web interface.</div><div><br></div><div>trying to do command line docker login and getting below error.</div><div><br></div><div>Error response from daemon: no successful auth challenge for <a href="http://192.168.1.20:5000/v2/">http://192.168.1.20:5000/v2/</a> - errors: []<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 19, 2016 at 10:16 PM, Miquel Sabaté Solà <span dir="ltr"><<a href="mailto:msabate@suse.de" target="_blank">msabate@suse.de</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><span class=""><br>
<br>
<div>On 01/19/2016 03:36 AM, Benjamin
Fernandis wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
<div>I am new with portus. Currently we are using docker v1
registry and just came to portus to use with docker v2 as we
are planning to move docker registry v2.</div>
<div><br>
</div>
<div>I downloaded appliance and trying to configure ldap
authentication but it is not working. Can you please suggest
me that where i can see logs for ldap.</div>
</div>
</div>
</blockquote>
<br></span>
First of all, the appliance holds a technical preview of Portus
which is quite old. We will correct that in the documentation. If
you are using SUSE, our recommendation is to use the RPM [1].<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
<div>I added ldap configuration
into /srv/Portus/config/config.yml</div>
</div>
</div>
</blockquote>
<br></span>
As described here [2], if you want to change the configuration of
Portus it's better to either create a config-local.yml file, or use
environment variables.<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
<div>
<div>settings:</div>
<div> gravatar: true</div>
<div><br>
</div>
<div>ldap:</div>
<div> enabled: true</div>
<div> hostname: hostname</div>
<div> port: 389</div>
<div> method: "plain"</div>
<div> base: "xyz"</div>
<div> uid: "uid" </div>
<div><br>
</div>
<div> guess_email:</div>
<div> enabled: true</div>
<div> attr: "mail"</div>
<div><br>
</div>
<div> authentication:</div>
<div> enabled: true</div>
<div> bind_dn: "xyz"</div>
<div> password: "xyz"</div>
</div>
<div><br>
</div>
</div>
<div><br>
</div>
<div>After this I rebooted appliance but no luck.</div>
<div><br>
</div>
<div>can we use portus as front end with existing docker
reigstry which is on v1?</div>
</div>
</blockquote>
<br></span>
No. Portus only works for version 2 of the registry. It's not
technically possible to support both versions, so we are focusing on
the latest (and production ready) version.<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>currently we have insecure registry setup.</div>
</div>
</blockquote>
<br></span>
That shouldn't be a problem (but of course we recommend a secure
registry ;), it's quite easy to do it actually [3]).<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<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>
You can find logs in /srv/Portus/log/production.log. That being
said, I would *really* encourage you to upgrade to the RPM setup.
The appliance is known to have bugs that have been long fixed in the
RPM. Another option, if you are just playing with Portus, is to try
our docker compose setup [4].<br>
<br>
Cheers,<br>
Miquel<br>
<br>
[1] <a href="http://port.us.org/docs/setups/1_rpm_packages.html" target="_blank">http://port.us.org/docs/setups/1_rpm_packages.html</a><br>
[2]
<a href="http://port.us.org/docs/Configuring-Portus.html#override-specific-configuration-options" target="_blank">http://port.us.org/docs/Configuring-Portus.html#override-specific-configuration-options</a><br>
[3] <a href="http://port.us.org/docs/How-to-setup-secure-registry.html" target="_blank">http://port.us.org/docs/How-to-setup-secure-registry.html</a><br>
[4] <a href="https://github.com/SUSE/Portus/wiki/Docker-Compose-Environment" target="_blank">https://github.com/SUSE/Portus/wiki/Docker-Compose-Environment</a><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></div>