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

Benjamin Fernandis benjo11111 at gmail.com
Sun Mar 13 18:46:07 MDT 2016


Hi Jordi,

while trying to update portus, it is not happenig. I guess due to different
name in new repo for 2.0.3

portus:~ # zypper info portus
Loading repository data...
Reading installed packages...


Information for package portus:
-------------------------------
Repository: 2.0.3 Release (openSUSE_Leap_42.1)
Name: portus
Version: 2.0.3-9.2
Arch: x86_64
Vendor: obs://build.opensuse.org/Virtualization
Installed: No
Status: not installed
Installed Size: 52.6 MiB
Summary: Authorization service and fronted for Docker registry (v2)
Description:
  Portus targets version 2 of the Docker registry API. It aims to act both
as an authoritzation server and as a user interface for the next generation
of the Docker registry.

  This package has been built with commit 2.0.3 from branch v2.0 on date
Tue, 08 Mar 2016 18:56:49 +0100

Information for package Portus:
-------------------------------
Repository: @System
Name: Portus
Version: 2.0.1-2.1
Arch: x86_64
Vendor: obs://build.opensuse.org/Virtualization
Installed: Yes
Status: up-to-date
Installed Size: 52.6 MiB
Summary: Authorization service and fronted for Docker registry (v2)
Description:
  Portus targets version 2 of the Docker registry API. It aims to act both
as an authoritzation server and as a user interface for the next generation
of the Docker registry.

  This package has been built with commit 2.0.0 from branch 2.0.0 on date
Tue, 15 Dec 2015 17:47:32 +0100



On Fri, Mar 11, 2016 at 2:00 AM, Jordi Massaguer Pla <jmassaguerpla at suse.de>
wrote:

>
>
> On 03/10/2016 10:38 AM, Jordi Massaguer Pla wrote:
>
> Hi,
>
> zypper update works fine.
>
> This same package will get a rebuild during today in order to include some
> security issues. Thus you may want to run zypper update tomorrow to get
> them.
>
>
> The package has been rebuild and now it includes patches for latest
> security issues found in some rubygems.
>
> cheers
>
> jordi
>
>
> cheers
>
> jordi
>
>
> On 03/10/2016 01:34 AM, Benjamin Fernandis wrote:
>
> Hi,
>
> Now i can see 2.0.3 , I want to upgrade my portus with this new rpm. Can i
> do straight upgrade , i mean zypper update portus or do i require to do
> specific way?
>
> On Wed, Mar 2, 2016 at 8:19 PM, Benjamin Fernandis <
> <benjo11111 at gmail.com>benjo11111 at gmail.com> wrote:
>
>> Thanks
>>
>>
>> On Tuesday, March 1, 2016, Miquel Sabaté Solà < <msabate at suse.com>
>> msabate at suse.com> wrote:
>>
>>> Hi Benjamin,
>>>
>>> We are still working on it, we had to fix some other issues first :) As
>>> soon as the new RPM is uploaded, I'll ping you back ;)
>>>
>>> Greetings,
>>> Miquel
>>>
>>> On 02/29/2016 10:16 PM, Benjamin Fernandis wrote:
>>>
>>> Thanks Miquel,
>>>
>>> From where I can download latest rpm for portus. As I am trying to get it
>>> but i got below versions from internet.
>>>
>>> Information for package Portus:
>>> -------------------------------
>>> Repository: 2.0.1 Release (openSUSE_Leap_42.1)
>>> Name: Portus
>>> Version: 2.0.1-2.1
>>> Arch: x86_64
>>> Vendor: obs://build.opensuse.org/Virtualization
>>> Installed: Yes
>>> Status: up-to-date
>>> Installed Size: 52.6 MiB
>>> Summary: Authorization service and fronted for Docker registry (v2)
>>> Description:
>>>   Portus targets version 2 of the Docker registry API. It aims to act both
>>> as an authoritzation server and as a user interface for the next generation
>>> of the Docker registry.
>>>
>>>   This package has been built with commit 2.0.0 from branch 2.0.0 on date
>>> Tue, 15 Dec 2015 17:47:32 +0100
>>>
>>> Information for package Portus:
>>> -------------------------------
>>> Repository: 2.0.0 Release (openSUSE_Leap_42.1)
>>> Name: Portus
>>> Version: 2.0.0-3.2
>>> Arch: x86_64
>>> Vendor: obs://build.opensuse.org/Virtualization
>>> Installed: No
>>> Status: not installed
>>> Installed Size: 52.6 MiB
>>> Summary: Authorization service and fronted for Docker registry (v2)
>>> Description:
>>>   Portus targets version 2 of the Docker registry API. It aims to act both
>>> as an authoritzation server and as a user interface for the next generation
>>> of the Docker registry.
>>>
>>>   This package has been built with commit 2.0.0 from branch 2.0.0 on date
>>> Tue, 15 Dec 2015 17:47:32 +0100
>>>
>>>
>>> And if i want to compile from source code , then what would be method, I
>>> tried to find install read me to get information like other tools require (
>>> configure, make, make install ).
>>>
>>> Regards
>>>
>>>
>>>
>>> On Fri, Feb 26, 2016 at 1:27 AM, Miquel Sabaté Solà <msabate at suse.com>
>>> wrote:
>>>
>>>
>>> Hi Benjamin,
>>>
>>> Portus 2.0.3 has been released [1]. We will update the RPM in the next
>>> days.
>>>
>>> Cheers,
>>> Miquel
>>>
>>> [1] https://github.com/SUSE/Portus/releases/tag/2.0.3
>>>
>>> On 02/18/2016 01:07 AM, Benjamin Fernandis wrote:
>>>
>>> Thanks Miquel,
>>>
>>> i setup portus by rpm on opensuse vm so wait for updated rpm.
>>>
>>> eager to see fix my problem.
>>>
>>> On Tue, Feb 16, 2016 at 9:36 PM, Miquel Sabaté Solà <msabate at suse.com>
>>> wrote:
>>>
>>>
>>> Hi there,
>>>
>>> This sounds very familiar actually. If I'm not mistaken this was fixed
>>> quite recently. The fix is already in both master and in the v2.0 branch.
>>> You can pull from these branches and test it again. That being said, we
>>> expect to release a 2.0.3 with this fix included soon enough (hopefully
>>> this friday).
>>>
>>> Greetings,
>>> Miquel
>>>
>>> On 02/16/2016 12:55 AM, Benjamin Fernandis wrote:
>>>
>>> Hi,
>>>
>>> after enable debug mode i can see below logs in portus log.i can see all
>>> logs like select . insert and all looks fine. but alos getting warning like
>>> below.
>>>
>>> please let me know if is there any configuration problem or , but still
>>> there is no data in portus web page for repositories.
>>>
>>>
>>>
>>> D, [2016-02-16T10:46:37.115000 #1145] DEBUG -- :   Registry Load (1.2ms)
>>>  SELECT  `registries`.* FROM `registries`  ORDER BY `registries`.`id` ASC
>>> LIMIT 1000
>>> D, [2016-02-16T10:46:37.677148 #1145] DEBUG -- :    (0.3ms)  BEGIN
>>> D, [2016-02-16T10:46:37.678519 #1145] DEBUG -- :    (0.5ms)  SELECT
>>> `repositories`.`id` FROM `repositories`
>>> D, [2016-02-16T10:46:37.679620 #1145] DEBUG -- :   Namespace Load (0.6ms)
>>>  SELECT  `namespaces`.* FROM `namespaces` WHERE `namespaces`.`name` =
>>> 'jack' LIMIT 1
>>> D, [2016-02-16T10:46:37.680299 #1145] DEBUG -- :    (0.2ms)  ROLLBACK
>>> W, [2016-02-16T10:46:37.680551 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> D, [2016-02-16T10:46:37.682409 #1145] DEBUG -- :   Crono::CronoJob Load
>>> (0.4ms)  SELECT  `crono_jobs`.* FROM `crono_jobs` WHERE `crono_jobs`.`id` =
>>> 2 LIMIT 1
>>>
>>>
>>>
>>> W, [2016-02-16T12:12:37.880039 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:14:37.885128 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:16:37.967088 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:18:38.087636 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:20:37.873064 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:22:37.900357 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:24:37.932614 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:26:37.916510 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:28:37.891098 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:30:37.916941 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:32:37.881212 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:34:37.906411 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:36:37.845196 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:38:37.857684 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:40:38.107515 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:42:37.885080 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:44:37.880108 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:46:37.885044 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:48:37.832047 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>> W, [2016-02-16T12:50:37.843278 #1145]  WARN -- : Exception: undefined
>>> method `id' for nil:NilClass
>>>
>>>
>>>
>>>
>>> On Sat, Feb 13, 2016 at 1:18 AM, Jordi Massaguer Pla <<jmassaguerpla at suse.de>jmassaguerpla at suse.de> wrote:
>>>
>>>
>>> look also in the apache2 logs, if you are using apache.
>>> you can add more debugging in config/environments/*.yml and also if you
>>> run passenger+apache, you can add more debugging to passenger
>>> (/etc/apache2/conf.d/... if you are using passenger rpm from SUSE).
>>>
>>>
>>> On 02/12/2016 12:36 AM, Benjamin Fernandis wrote:
>>>
>>> is there a way to enable debug mode in portus to see what happening. As
>>> can't find anything in logs.
>>>
>>> On Fri, Feb 12, 2016 at 12:17 PM, Benjamin Fernandis <<benjo11111 at gmail.com>benjo11111 at gmail.com> wrote:
>>>
>>>
>>> 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>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> <http://port.us.org/features/1_Synchronizing-the-Registry-and-Portus.html>http://port.us.org/features/1_Synchronizing-the-Registry-and-Portus.html
>>> [2] <https://github.com/SUSE/Portus/issues/720> <https://github.com/SUSE/Portus/issues/720>https://github.com/SUSE/Portus/issues/720
>>>
>>> _______________________________________________
>>> Containers mailing list<Containers at lists.suse.com>Containers at lists.suse.com<http://lists.suse.com/mailman/listinfo/containers> <http://lists.suse.com/mailman/listinfo/containers>http://lists.suse.com/mailman/listinfo/containers
>>>
>>>  _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>  _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>  _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>
>
>
>
> _______________________________________________
> 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/20160314/809099f0/attachment.htm>


More information about the Containers mailing list