From benjo11111 at gmail.com  Wed Mar  2 00:19:57 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Wed, 2 Mar 2016 20:19:57 +1300
Subject: [Containers] portus integration with existing running docker
	v2.2 registry
In-Reply-To: <56D54DA0.4050809@suse.com>
References: <CAARrgqwEfP3f=HffrvBA9AS15m21kLWvhZiRFeEKi4_YqPrRPg@mail.gmail.com>
	<56BC8B91.4070807@suse.com>
	<CAARrgqxfNtdx7eM19+n1f6yDy9ECRxCe=BPrsp8Ld4bH5e=F_Q@mail.gmail.com>
	<CAARrgqxtQoEg_no3ib78pkEU+R5EE1OKgkfVNzHsfCjKwVoLTw@mail.gmail.com>
	<56BDCD8A.80100@suse.de>
	<CAARrgqysXw5+_057Z1EzdOMFYnSXQZD1B3FL7BKwOGw5mkfGmg@mail.gmail.com>
	<56C2DF9C.4080705@suse.com>
	<CAARrgqzhwH17UJWzed_sdFLpUxW6cHWw2R1wuHDQLR+n=mPugA@mail.gmail.com>
	<56CEF34B.9010709@suse.com>
	<CAARrgqw3Vd6mMcGbFQmn2WF0J85zLT2J-J3jYEeuaeyFgLv8LA@mail.gmail.com>
	<56D54DA0.4050809@suse.com>
Message-ID: <CAARrgqztVT1ntG0-w9fbYdjf7+OqHx933zFw97M3mgVZ5epq=Q@mail.gmail.com>

Thanks

On Tuesday, March 1, 2016, Miquel Sabat? Sol? <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> <javascript:_e(%7B%7D,'cvml','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> <javascript:_e(%7B%7D,'cvml','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> <javascript:_e(%7B%7D,'cvml','jmassaguerpla at suse.de');>jmassaguerpla at suse.de <javascript:_e(%7B%7D,'cvml','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> <javascript:_e(%7B%7D,'cvml','benjo11111 at gmail.com');>benjo11111 at gmail.com <javascript:_e(%7B%7D,'cvml','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> <javascript:_e(%7B%7D,'cvml','msabate at suse.com');>msabate at suse.com <javascript:_e(%7B%7D,'cvml','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 <javascript:_e(%7B%7D,'cvml','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> <javascript:_e(%7B%7D,'cvml','Containers at lists.suse.com');>Containers at lists.suse.com <javascript:_e(%7B%7D,'cvml','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 <javascript:_e(%7B%7D,'cvml','listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers');>
>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.com <javascript:_e(%7B%7D,'cvml','Containers at lists.suse.com');>http://lists.suse.com/mailman/listinfo/containers
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers <javascript:_e(%7B%7D,'cvml','listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers');>
>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.com <javascript:_e(%7B%7D,'cvml','Containers at lists.suse.com');>http://lists.suse.com/mailman/listinfo/containers
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers <javascript:_e(%7B%7D,'cvml','listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers');>
>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.com <javascript:_e(%7B%7D,'cvml','Containers at lists.suse.com');>http://lists.suse.com/mailman/listinfo/containers
>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.com <javascript:_e(%7B%7D,'cvml','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/20160302/43be496e/attachment.htm>

From asarai at suse.com  Wed Mar  2 01:10:36 2016
From: asarai at suse.com (Aleksa Sarai)
Date: Wed, 2 Mar 2016 19:10:36 +1100
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
Message-ID: <56D69FFC.5060605@suse.com>

On 03/02/2016 06:28 PM, Bell, Bob (ENG Nashua) wrote:
> Are there SLES Docker images available to the general public?  Yes, I
> know about the sles12-docker-image RPM that gives /me/ the
> /usr/share/suse-docker-images/sles12-docker.x86_64-*.tar.xz image.  But
> what about for the community?  Or at least maybe select subgroups of the
> community?

No, they aren't AFAIK. We do have Leap images though (opensuse:leap), 
and since Leap is the publically available version of SLES, is that 
sufficient?

> I?m working with the Git LFS team, and they don?t have RPMs for any SUSE
> release.  I?d love for them to be able to build and supply a SLES 12 RPM
> (and an openSUSE one would be nice, too).  The maintainer?s requirement
> to build and support Git LFS for a distribution is to be have to have a
> Docker container where he can build and test the Git LFS binary.

Is there a reason we can't just give them an openSUSE docker image (from 
the registry) and then adapt the build script they give us? Also, since 
we have Leap, surely that's sufficiently similar to SLES to be 
indistinguishable from a "making a preliminary build script" perspective?

Or are you suggesting that a SLES package will be maintained by an 
external party?

-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From asarai at suse.com  Wed Mar  2 01:18:24 2016
From: asarai at suse.com (Aleksa Sarai)
Date: Wed, 2 Mar 2016 19:18:24 +1100
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <56D69FFC.5060605@suse.com>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
	<56D69FFC.5060605@suse.com>
Message-ID: <56D6A1D0.1010909@suse.com>

 > Is there a reason we can't just give them an openSUSE docker image (from
 > the registry) and then adapt the build script they give us? Also, since
 > we have Leap, surely that's sufficiently similar to SLES to be
 > indistinguishable from a "making a preliminary build script" perspective?
 >
 > Or are you suggesting that a SLES package will be maintained by an
 > external party?

Oh sorry, I didn't realise that you weren't from SUSE. In that case, 
telling them to use a Leap image to build the RPM could work (I'm not 
entirely sure about that though, you'll have to ask Flavio about the 
difference between the Leap and SLES Docker images).

-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From fcastelli at suse.com  Wed Mar  2 01:18:15 2016
From: fcastelli at suse.com (Flavio Castelli)
Date: Wed, 2 Mar 2016 09:18:15 +0100
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
Message-ID: <56D6A1C7.1080508@suse.com>

On 03/02/2016 08:28 AM, Bob (ENG Nashua) Bell wrote:
> I did find a recent openSUSE Docker image through the Docker repository, but nothing for SLES.  I understand why access might be limited (as a paid-for product), but is there anything we can do so that the maintainer can support SLES?  I don't think he's going to want to use OBS just to create binaries for one type of distribution (which he then can't even properly test himself).

We would like to put the SLE images on the Docker Hub. We are not doing 
that right now because we don't want to break the chain of trust. We 
don't know how the Docker Hub manages the security of their systems plus 
we would depend on them for the updates. The update procedure consists 
of a PR against a github repo, so we would have to wait for the 
maintainers of this repo to merge our PR and we would have to trust them 
to not accept requests from random people claiming to be SUSE.

We are waiting for Docker to support signed images out of the box, right 
now this feature is still experimental.

Cheers
Flavio

From Robert.Bell at emc.com  Wed Mar  2 10:15:36 2016
From: Robert.Bell at emc.com (Bob Bell)
Date: Wed, 2 Mar 2016 12:15:36 -0500
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <56D6A1D0.1010909@suse.com>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
	<56D69FFC.5060605@suse.com> <56D6A1D0.1010909@suse.com>
Message-ID: <20160302171535.GA20043@robin.thebellsplace.net>

On Wed, Mar 02, 2016 at 07:18:24PM +1100, Aleksa Sarai wrote:
>> Is there a reason we can't just give them an openSUSE docker image (from
>> the registry) and then adapt the build script they give us? Also, since
>> we have Leap, surely that's sufficiently similar to SLES to be
>> indistinguishable from a "making a preliminary build script" perspective?
>>
>> Or are you suggesting that a SLES package will be maintained by an
>> external party?
>
>Oh sorry, I didn't realise that you weren't from SUSE. In that case, 
>telling them to use a Leap image to build the RPM could work (I'm not 
>entirely sure about that though, you'll have to ask Flavio about the 
>difference between the Leap and SLES Docker images).

I'll take it as a compliment that you thought I was from SUSE. :)

I hadn't heard of Leap before.  I took a look, and that could work.

To be clear, we are talking about the 42.1 / leap references from 
https://hub.docker.com/_/opensuse/, right?  The Dockerfile says it's 
maintained by Flavio, so I'm guessing that that right one.

And from what I can see, 42.1 would be a match to SLES12 SP1 (no match 
for SLES12 GA from Leap, I guess, but hopefully that doesn't matter).

-- Bob

From jmassaguerpla at suse.de  Wed Mar  2 10:24:58 2016
From: jmassaguerpla at suse.de (Jordi Massaguer Pla)
Date: Wed, 2 Mar 2016 18:24:58 +0100
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <20160302171535.GA20043@robin.thebellsplace.net>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
	<56D69FFC.5060605@suse.com> <56D6A1D0.1010909@suse.com>
	<20160302171535.GA20043@robin.thebellsplace.net>
Message-ID: <56D721EA.3020508@suse.de>



On 03/02/2016 06:15 PM, Bob Bell wrote:
> On Wed, Mar 02, 2016 at 07:18:24PM +1100, Aleksa Sarai wrote:
>>> Is there a reason we can't just give them an openSUSE docker image (from
>>> the registry) and then adapt the build script they give us? Also, since
>>> we have Leap, surely that's sufficiently similar to SLES to be
>>> indistinguishable from a "making a preliminary build script" perspective?
>>>
>>> Or are you suggesting that a SLES package will be maintained by an
>>> external party?
>> Oh sorry, I didn't realise that you weren't from SUSE. In that case,
>> telling them to use a Leap image to build the RPM could work (I'm not
>> entirely sure about that though, you'll have to ask Flavio about the
>> difference between the Leap and SLES Docker images).
> I'll take it as a compliment that you thought I was from SUSE. :)
>
> I hadn't heard of Leap before.  I took a look, and that could work.
>
> To be clear, we are talking about the 42.1 / leap references from
> https://hub.docker.com/_/opensuse/, right?  The Dockerfile says it's
> maintained by Flavio, so I'm guessing that that right one.
>
> And from what I can see, 42.1 would be a match to SLES12 SP1 (no match
> for SLES12 GA from Leap, I guess, but hopefully that doesn't matter).

openSUSE Leap is the same as openSUSE 42.1 . SLE-12 codebase is shared 
with that version. SLE-12-SP1 has the same codebase, so, in general, it 
shouldn't matter.

> -- Bob
> _______________________________________________
> Containers mailing list
> Containers at lists.suse.com
> http://lists.suse.com/mailman/listinfo/containers


From asarai at suse.com  Wed Mar  2 13:48:06 2016
From: asarai at suse.com (Aleksa Sarai)
Date: Thu, 3 Mar 2016 07:48:06 +1100
Subject: [Containers] Availability of SLES docker images
In-Reply-To: <20160302171535.GA20043@robin.thebellsplace.net>
References: <A3B66DB614F06142905C2540102EBA2B2995BA0A@MX108CL02.corp.emc.com>
	<56D69FFC.5060605@suse.com> <56D6A1D0.1010909@suse.com>
	<20160302171535.GA20043@robin.thebellsplace.net>
Message-ID: <56D75186.3050008@suse.com>

> I hadn't heard of Leap before.  I took a look, and that could work.

Yeah, it's fairly a new distribution of openSUSE (and we need to do a 
better job of advertising it IMO).

> To be clear, we are talking about the 42.1 / leap references from
> https://hub.docker.com/_/opensuse/, right?  The Dockerfile says it's
> maintained by Flavio, so I'm guessing that that right one.

Yup. :D

-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From pszewczuk at suse.com  Mon Mar  7 03:21:08 2016
From: pszewczuk at suse.com (Piotr Szewczuk)
Date: Mon, 07 Mar 2016 11:21:08 +0100
Subject: [Containers] SLES Docker + HA
References: <56D9A950020000F2000BF85C@smtp.nue.novell.com>
	<56DD6424020000F2000BF9ED@smtp.nue.novell.com>
Message-ID: <56DD6424020000F2000BF9ED@smtp.nue.novell.com>


Hello, 

My customer wants to know what is our recommended and supported environment for clustering docker. 
In small environment can we run Docker with SLES HA and DRBD. Just like is outlined here: 
https://www.thomas-krenn.com/en/wiki/HA_Cluster_with_Linux_Containers_based_on_Heartbeat,_Pacemaker,_DRBD_and_LXC 
The second question is whether we support Docker Swarm? 
https://docs.docker.com/swarm/install-manual/ 

Best regards, 
Piotr Szewczuk 
Piotr Szewczuk
Konsultant

Micro Focus | SUSE
ul. Post?pu 21
02-676 Warszawa
tel. +48 22 537 5000
pszewczuk at suse.com

Przedstawicielstwo krajowe firm Micro Focus i SUSE oferuj?cych rozwi?zania:
Attachmate | Borland | Micro Focus | NetIQ | Novell | SUSE



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160307/e2d461a1/attachment.htm>

From fcastelli at suse.com  Mon Mar  7 04:31:25 2016
From: fcastelli at suse.com (Flavio Castelli)
Date: Mon, 7 Mar 2016 12:31:25 +0100
Subject: [Containers] SLES Docker + HA
In-Reply-To: <56DD6424020000F2000BF9ED@smtp.nue.novell.com>
References: <56D9A950020000F2000BF85C@smtp.nue.novell.com>
	<56DD6424020000F2000BF9ED@smtp.nue.novell.com>
	<56DD6424020000F2000BF9ED@smtp.nue.novell.com>
Message-ID: <56DD668D.7000908@suse.com>

On 03/07/2016 11:21 AM, Piotr Szewczuk wrote:
> My customer wants to know what is our recommended and supported environment for clustering docker.
> In small environment can we run Docker with SLES HA and DRBD. Just like is outlined here:
> https://www.thomas-krenn.com/en/wiki/HA_Cluster_with_Linux_Containers_based_on_Heartbeat,_Pacemaker,_DRBD_and_LXC

This documentation is about linux containers using LXC. Nothing prevents 
you from using the same techniques with Docker. However there are 
dedicated orchestration solutions for Docker containers that allow you 
to manage a cluster of Docker hosts.

> The second question is whether we support Docker Swarm?
> https://docs.docker.com/swarm/install-manual/

We are currently evaluating different orchestration solutions for Docker 
containers. We are going to deliver one as part of our next milestone. 
In the meantime it would be interesting to know the requirements and use 
cases of your customer.

Cheers
Flavio

From fahimehashrafy at gmail.com  Mon Mar  7 22:09:21 2016
From: fahimehashrafy at gmail.com (Fahimeh Ashrafy)
Date: Tue, 8 Mar 2016 08:39:21 +0330
Subject: [Containers] container monitoring
Message-ID: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>

Hello all

what is the best tools to monitor i/o, filesystem,cpu, memory, ...of each
container either on one node or multinode?
 i/o, filesystem are the most important ones to monitor.

Thanks a lot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160308/4aa7a35a/attachment.htm>

From fahimehashrafy at gmail.com  Tue Mar  8 10:01:34 2016
From: fahimehashrafy at gmail.com (Fahimeh Ashrafy)
Date: Tue, 8 Mar 2016 20:31:34 +0330
Subject: [Containers] container monitoring
In-Reply-To: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>
References: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>
Message-ID: <CALZ4PNpJ+2X-nOpamHfG8qjsuauNk4PAGakoV33XBM2nzUTyZw@mail.gmail.com>

no help?

On Tue, Mar 8, 2016 at 8:39 AM, Fahimeh Ashrafy <fahimehashrafy at gmail.com>
wrote:

> Hello all
>
> what is the best tools to monitor i/o, filesystem,cpu, memory, ...of each
> container either on one node or multinode?
>  i/o, filesystem are the most important ones to monitor.
>
> Thanks a lot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160308/c5195f0f/attachment.htm>

From asarai at suse.com  Tue Mar  8 15:40:49 2016
From: asarai at suse.com (Aleksa Sarai)
Date: Wed, 9 Mar 2016 09:40:49 +1100
Subject: [Containers] container monitoring
In-Reply-To: <CALZ4PNpJ+2X-nOpamHfG8qjsuauNk4PAGakoV33XBM2nzUTyZw@mail.gmail.com>
References: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>
	<CALZ4PNpJ+2X-nOpamHfG8qjsuauNk4PAGakoV33XBM2nzUTyZw@mail.gmail.com>
Message-ID: <56DF54F1.1020302@suse.com>

>     Hello all
>
>     what is the best tools to monitor i/o, filesystem,cpu, memory, ...of
>     each container either on one node or multinode?
>       i/o, filesystem are the most important ones to monitor.

On a single-node basis, you can get /some/ information from `docker 
stats`, which uses information from the related cgroups of the 
containers (this includes both the usage and limit for most of things 
you mention -- though I'm not sure what you mean by "filesystem"). 
There's a new feature that's being worked on in Docker to allow a 
container to join the cgroups of another container, once that's done you 
could run a container with your tooling and connect it to a container 
you want to monitor and then scoop up the output (see next point).

As for multi-node, I'm not really sure if there's a dedicated tool. You 
could try playing with something like logstash and elasticsearch to 
"log" the usage statistics and do analytics on them. I've never use 
logstash personally, so I can't really comment on how well that would 
work for your usecase (which you haven't told us).

-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From asarai at suse.de  Tue Mar  8 15:43:22 2016
From: asarai at suse.de (Aleksa Sarai)
Date: Wed, 9 Mar 2016 09:43:22 +1100
Subject: [Containers] container monitoring
In-Reply-To: <56DF54F1.1020302@suse.com>
References: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>
	<CALZ4PNpJ+2X-nOpamHfG8qjsuauNk4PAGakoV33XBM2nzUTyZw@mail.gmail.com>
	<56DF54F1.1020302@suse.com>
Message-ID: <56DF558A.5000507@suse.de>

> As for multi-node, I'm not really sure if there's a dedicated tool. You
> could try playing with something like logstash and elasticsearch to
> "log" the usage statistics and do analytics on them. I've never use
> logstash personally, so I can't really comment on how well that would
> work for your usecase (which you haven't told us).

Whoops, I missed the list Jordi posted: 
http://rancher.com/comparing-monitoring-options-for-docker-deployments/


-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From asarai at suse.de  Tue Mar  8 15:47:33 2016
From: asarai at suse.de (Aleksa Sarai)
Date: Wed, 9 Mar 2016 09:47:33 +1100
Subject: [Containers] container monitoring
In-Reply-To: <56DF558A.5000507@suse.de>
References: <CALZ4PNq29KrPORp=hFDgEftiRLpVs7rfzOGFuV8ROuXjebB3gg@mail.gmail.com>
	<CALZ4PNpJ+2X-nOpamHfG8qjsuauNk4PAGakoV33XBM2nzUTyZw@mail.gmail.com>
	<56DF54F1.1020302@suse.com> <56DF558A.5000507@suse.de>
Message-ID: <56DF5685.4050207@suse.de>

On 09/03/16 09:43, Aleksa Sarai wrote:
>> As for multi-node, I'm not really sure if there's a dedicated tool. You
>> could try playing with something like logstash and elasticsearch to
>> "log" the usage statistics and do analytics on them. I've never use
>> logstash personally, so I can't really comment on how well that would
>> work for your usecase (which you haven't told us).
>
> Whoops, I missed the list Jordi posted:
> http://rancher.com/comparing-monitoring-options-for-docker-deployments/

And here's a pre-existing tool I found from a bit of Googling for doing 
this sort of monitoring with logstash, elasticsearch and kibana: 
https://github.com/cilium-team/docker-collector.


-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From benjo11111 at gmail.com  Wed Mar  9 17:34:44 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Thu, 10 Mar 2016 13:34:44 +1300
Subject: [Containers] portus integration with existing running docker
	v2.2 registry
In-Reply-To: <CAARrgqztVT1ntG0-w9fbYdjf7+OqHx933zFw97M3mgVZ5epq=Q@mail.gmail.com>
References: <CAARrgqwEfP3f=HffrvBA9AS15m21kLWvhZiRFeEKi4_YqPrRPg@mail.gmail.com>
	<56BC8B91.4070807@suse.com>
	<CAARrgqxfNtdx7eM19+n1f6yDy9ECRxCe=BPrsp8Ld4bH5e=F_Q@mail.gmail.com>
	<CAARrgqxtQoEg_no3ib78pkEU+R5EE1OKgkfVNzHsfCjKwVoLTw@mail.gmail.com>
	<56BDCD8A.80100@suse.de>
	<CAARrgqysXw5+_057Z1EzdOMFYnSXQZD1B3FL7BKwOGw5mkfGmg@mail.gmail.com>
	<56C2DF9C.4080705@suse.com>
	<CAARrgqzhwH17UJWzed_sdFLpUxW6cHWw2R1wuHDQLR+n=mPugA@mail.gmail.com>
	<56CEF34B.9010709@suse.com>
	<CAARrgqw3Vd6mMcGbFQmn2WF0J85zLT2J-J3jYEeuaeyFgLv8LA@mail.gmail.com>
	<56D54DA0.4050809@suse.com>
	<CAARrgqztVT1ntG0-w9fbYdjf7+OqHx933zFw97M3mgVZ5epq=Q@mail.gmail.com>
Message-ID: <CAARrgqzLJH+E3O+Cj8dbRiMkr4O=7eAD9AsuGQX9LddG4h4iSw@mail.gmail.com>

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>
wrote:

> Thanks
>
>
> On Tuesday, March 1, 2016, Miquel Sabat? Sol? <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
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160310/c6166978/attachment.htm>

From benjo11111 at gmail.com  Sun Mar 13 18:46:07 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Mon, 14 Mar 2016 13:46:07 +1300
Subject: [Containers] portus integration with existing running docker
	v2.2 registry
In-Reply-To: <56E16FDD.6040008@suse.de>
References: <CAARrgqwEfP3f=HffrvBA9AS15m21kLWvhZiRFeEKi4_YqPrRPg@mail.gmail.com>
	<56BC8B91.4070807@suse.com>
	<CAARrgqxfNtdx7eM19+n1f6yDy9ECRxCe=BPrsp8Ld4bH5e=F_Q@mail.gmail.com>
	<CAARrgqxtQoEg_no3ib78pkEU+R5EE1OKgkfVNzHsfCjKwVoLTw@mail.gmail.com>
	<56BDCD8A.80100@suse.de>
	<CAARrgqysXw5+_057Z1EzdOMFYnSXQZD1B3FL7BKwOGw5mkfGmg@mail.gmail.com>
	<56C2DF9C.4080705@suse.com>
	<CAARrgqzhwH17UJWzed_sdFLpUxW6cHWw2R1wuHDQLR+n=mPugA@mail.gmail.com>
	<56CEF34B.9010709@suse.com>
	<CAARrgqw3Vd6mMcGbFQmn2WF0J85zLT2J-J3jYEeuaeyFgLv8LA@mail.gmail.com>
	<56D54DA0.4050809@suse.com>
	<CAARrgqztVT1ntG0-w9fbYdjf7+OqHx933zFw97M3mgVZ5epq=Q@mail.gmail.com>
	<CAARrgqzLJH+E3O+Cj8dbRiMkr4O=7eAD9AsuGQX9LddG4h4iSw@mail.gmail.com>
	<56E14098.9060700@suse.de> <56E16FDD.6040008@suse.de>
Message-ID: <CAARrgqycab9d77p9oBd6YTTqzgnL3jJQ2ehsQdoQkBBAsBDGTQ@mail.gmail.com>

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>

From benjo11111 at gmail.com  Mon Mar 14 14:36:42 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Tue, 15 Mar 2016 09:36:42 +1300
Subject: [Containers] portus integration with existing running docker
	v2.2 registry
In-Reply-To: <56E67B0E.3070700@suse.de>
References: <CAARrgqwEfP3f=HffrvBA9AS15m21kLWvhZiRFeEKi4_YqPrRPg@mail.gmail.com>
	<56BC8B91.4070807@suse.com>
	<CAARrgqxfNtdx7eM19+n1f6yDy9ECRxCe=BPrsp8Ld4bH5e=F_Q@mail.gmail.com>
	<CAARrgqxtQoEg_no3ib78pkEU+R5EE1OKgkfVNzHsfCjKwVoLTw@mail.gmail.com>
	<56BDCD8A.80100@suse.de>
	<CAARrgqysXw5+_057Z1EzdOMFYnSXQZD1B3FL7BKwOGw5mkfGmg@mail.gmail.com>
	<56C2DF9C.4080705@suse.com>
	<CAARrgqzhwH17UJWzed_sdFLpUxW6cHWw2R1wuHDQLR+n=mPugA@mail.gmail.com>
	<56CEF34B.9010709@suse.com>
	<CAARrgqw3Vd6mMcGbFQmn2WF0J85zLT2J-J3jYEeuaeyFgLv8LA@mail.gmail.com>
	<56D54DA0.4050809@suse.com>
	<CAARrgqztVT1ntG0-w9fbYdjf7+OqHx933zFw97M3mgVZ5epq=Q@mail.gmail.com>
	<CAARrgqzLJH+E3O+Cj8dbRiMkr4O=7eAD9AsuGQX9LddG4h4iSw@mail.gmail.com>
	<56E14098.9060700@suse.de> <56E16FDD.6040008@suse.de>
	<CAARrgqycab9d77p9oBd6YTTqzgnL3jJQ2ehsQdoQkBBAsBDGTQ@mail.gmail.com>
	<56E67B0E.3070700@suse.de>
Message-ID: <CAARrgqy1-yt9zCb8rAOEP+GOasUfnbKG+7LN9FNWJhwo5e5rcA@mail.gmail.com>

Hi,

Below result from my vm, Here if i go to last output, it says remove
current version and install new one, so in that case, does affect my
current running portus? I mean it is same like update or ?

Do i require to re-setup portus or ?

portus:~ # zypper in portus
Loading repository data...
Reading installed packages...
'Portus' providing 'portus' is already installed.
Package 'Portus' is not available in your repositories. Cannot reinstall,
upgrade, or downgrade.
Resolving package dependencies...

Nothing to do.
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
portus:~ # zypper in portus
Loading repository data...
Reading installed packages...
'Portus' providing 'portus' is already installed.
Package 'Portus' is not available in your repositories. Cannot reinstall,
upgrade, or downgrade.
Resolving package dependencies...

Nothing to do.
portus:~ # zypper in portus-2.0.3-9.2
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  portus

The following package is going to be REMOVED:
  Portus

1 new package to install, 1 to remove.
Overall download size: 31.7 MiB. Already cached: 0 B. After the operation,
additional 10.1 KiB will be used.
Continue? [y/n/? shows all options] (y):


On Mon, Mar 14, 2016 at 9:49 PM, Jordi Massaguer Pla <jmassaguerpla at suse.de>
wrote:

> Hi,
>
> the rename is fine and expected. What does "zypper install Portus" tells
> you? Doesn't give you the option to install new portus-2.0.3?
>
> jordi
>
>
> On 03/14/2016 01:46 AM, Benjamin Fernandis wrote:
>
> 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> 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
>>
>>
>
>
> _______________________________________________
> 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/20160315/28b828ee/attachment.htm>

From benjo11111 at gmail.com  Thu Mar 17 16:28:17 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Fri, 18 Mar 2016 11:28:17 +1300
Subject: [Containers] Auto redirect http to https for portus web inteface
Message-ID: <CAARrgqzGk_TORpT994W+qeDSJXBbRwzsr3_=wwnun445nEOLRQ@mail.gmail.com>

Hi,

How we can do auto-redirect http to https for portus web interface.

As when we do http, it gives some error but with https it works fine.

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160318/2ee14b7d/attachment.htm>

From asarai at suse.com  Thu Mar 17 16:39:27 2016
From: asarai at suse.com (Aleksa Sarai)
Date: Fri, 18 Mar 2016 09:39:27 +1100
Subject: [Containers] Auto redirect http to https for portus web inteface
In-Reply-To: <CAARrgqzGk_TORpT994W+qeDSJXBbRwzsr3_=wwnun445nEOLRQ@mail.gmail.com>
References: <CAARrgqzGk_TORpT994W+qeDSJXBbRwzsr3_=wwnun445nEOLRQ@mail.gmail.com>
Message-ID: <56EB321F.2020302@suse.com>


> How we can do auto-redirect http to https for portus web interface.
>
> As when we do http, it gives some error but with https it works fine.

Is your Portus server behind Nginx? If so, you can just add the 
following directive:

server {
	listen 80;
	server_name <same as your SSL setup>;

	return 301 https://$host$request_url;
}

You can swap 301 (permanent) for 302 (temporary).

-- 
Aleksa Sarai
Docker Core Specialist
SUSE Australia
https://www.cyphar.com/

From benjo11111 at gmail.com  Thu Mar 17 17:35:34 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Fri, 18 Mar 2016 12:35:34 +1300
Subject: [Containers] Auto redirect http to https for portus web inteface
In-Reply-To: <56EB321F.2020302@suse.com>
References: <CAARrgqzGk_TORpT994W+qeDSJXBbRwzsr3_=wwnun445nEOLRQ@mail.gmail.com>
	<56EB321F.2020302@suse.com>
Message-ID: <CAARrgqy3P5qJR-4431HFTU36wWx=FWWXHJ=1w=K-JmwcVzvydQ@mail.gmail.com>

Hi, I setup portus by rpm onn opensuse, I m thinking it comes with inbuilt
apache + mode_pessenger.

On Fri, Mar 18, 2016 at 11:39 AM, Aleksa Sarai <asarai at suse.com> wrote:

>
> How we can do auto-redirect http to https for portus web interface.
>>
>> As when we do http, it gives some error but with https it works fine.
>>
>
> Is your Portus server behind Nginx? If so, you can just add the following
> directive:
>
> server {
>         listen 80;
>         server_name <same as your SSL setup>;
>
>         return 301 https://$host$request_url;
> }
>
> You can swap 301 (permanent) for 302 (temporary).
>
> --
> Aleksa Sarai
> Docker Core Specialist
> SUSE Australia
> https://www.cyphar.com/
> _______________________________________________
> 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/20160318/89350a5f/attachment.htm>

From benjo11111 at gmail.com  Sun Mar 20 19:14:12 2016
From: benjo11111 at gmail.com (Benjamin Fernandis)
Date: Mon, 21 Mar 2016 14:14:12 +1300
Subject: [Containers] Auto redirect http to https for portus web inteface
In-Reply-To: <56EBC3E9.8070903@suse.de>
References: <CAARrgqzGk_TORpT994W+qeDSJXBbRwzsr3_=wwnun445nEOLRQ@mail.gmail.com>
	<56EB321F.2020302@suse.com>
	<CAARrgqy3P5qJR-4431HFTU36wWx=FWWXHJ=1w=K-JmwcVzvydQ@mail.gmail.com>
	<56EBC3E9.8070903@suse.de>
Message-ID: <CAARrgqzuvW4+sONspn+c3QGSSgzUYDoy9PoX=5ZLYrp+Vm3k1A@mail.gmail.com>

yep, now working

Thanks Jordi

On Fri, Mar 18, 2016 at 10:01 PM, Jordi Massaguer Pla <jmassaguerpla at suse.de
> wrote:

> Then you can try with https://wiki.apache.org/httpd/RedirectSSL
>
>
> On 03/18/2016 12:35 AM, Benjamin Fernandis wrote:
>
> Hi, I setup portus by rpm onn opensuse, I m thinking it comes with inbuilt
> apache + mode_pessenger.
>
> On Fri, Mar 18, 2016 at 11:39 AM, Aleksa Sarai <asarai at suse.com> wrote:
>
>>
>> How we can do auto-redirect http to https for portus web interface.
>>>
>>> As when we do http, it gives some error but with https it works fine.
>>>
>>
>> Is your Portus server behind Nginx? If so, you can just add the following
>> directive:
>>
>> server {
>>         listen 80;
>>         server_name <same as your SSL setup>;
>>
>>         return 301 https://$host$request_url;
>> }
>>
>> You can swap 301 (permanent) for 302 (temporary).
>>
>> --
>> Aleksa Sarai
>> Docker Core Specialist
>> SUSE Australia
>> https://www.cyphar.com/
>> _______________________________________________
>> Containers mailing list
>> Containers at lists.suse.com
>> http://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/20160321/0cfe9573/attachment.htm>