As more and more services are distributed as docker images and most
modern continuous integration services rely on docker images to do
their work, I think it would be useful to have an OSGeo docker
registry where OSGeo projects can push their images, using the OSGeo
Userid as authentication.
I've setup a private registry on my own host and started using it
for fetching build-test images for PostGIS, GEOS and Librttopo,
but my test setup doesn't use the OSGeo LDAP for authentication.
The space taken by my 4 docker images is currently 2.6G.
I guess it may grow easily, but space shouldn't be a big issue
these days, right ?
As we've been discussing about getting more disk space for
the "download" machine, can we take in account a possible
increase in disk space due to serving docker images too ?
Or should we just surrender to the centralization of docker hub ?
On 25 July 2016 at 12:14, Sandro Santilli <strk@kbt.io> wrote:
As more and more services are distributed as docker images and most
modern continuous integration services rely on docker images to do
their work, I think it would be useful to have an OSGeo docker
registry where OSGeo projects can push their images, using the OSGeo
Userid as authentication.'
Sandro,
How it could be useful exactly?
Can you outline any use cases directly applicable to OSGeo
activities or projects?
Hi Sandro: valuable idea, thanks for bringing this up! Items
for consideration:
- if we use Docker Hub are there any technical limitations (size, number
of repos) that would justify us standing up our own?
- if we use Docker Hub is there a backout strategy if there are technical
or non technical reasons to do so?
Given our limited and precious reosurces I would advocate for using Docker
Hub with an OSGeo organization setup and have an internal setup for
protected/sensitive/OSGeo Dockerfile's where required.
..Tom
On Mon, 25 Jul 2016, Sandro Santilli wrote:
Date: Mon, 25 Jul 2016 12:14:02 +0200
From: Sandro Santilli <strk@kbt.io>
Reply-To: System Administration Committee Discussion/OSGeo
<sac@lists.osgeo.org>, sac@lists.osgeo.org,
Alex Mandel <tech@wildintellect.com>
To: sac@lists.osgeo.org
Subject: [SAC] Running an osgeo docker registry
As more and more services are distributed as docker images and most
modern continuous integration services rely on docker images to do
their work, I think it would be useful to have an OSGeo docker
registry where OSGeo projects can push their images, using the OSGeo
Userid as authentication.
I've setup a private registry on my own host and started using it
for fetching build-test images for PostGIS, GEOS and Librttopo,
but my test setup doesn't use the OSGeo LDAP for authentication.
The space taken by my 4 docker images is currently 2.6G.
I guess it may grow easily, but space shouldn't be a big issue
these days, right ?
As we've been discussing about getting more disk space for
the "download" machine, can we take in account a possible
increase in disk space due to serving docker images too ?
Or should we just surrender to the centralization of docker hub ?
I created an existing OSGeo DockerHub organization a while ago (there's a Proj.4 image there, but it isn't really used for anything other than testing and confirmation). Please contact me if you wish to manage or push new images to it.
On Jul 25, 2016, at 6:12 AM, Tom Kralidis <tomkralidis@gmail.com> wrote:
Hi Sandro: valuable idea, thanks for bringing this up! Items
for consideration:
- if we use Docker Hub are there any technical limitations (size, number
of repos) that would justify us standing up our own?
None if they are all open.
- if we use Docker Hub is there a backout strategy if there are technical
or non technical reasons to do so?
We just run our own repository if we need to leave DH.
Given our limited and precious reosurces I would advocate for using Docker
Hub with an OSGeo organization setup and have an internal setup for
protected/sensitive/OSGeo Dockerfile's where required.
Me too, especially considering that every docker install will seamlessly consume images from DockerHub, and private repos require adding certificates -- which users can easily goof up.
As more and more services are distributed as docker images and most
modern continuous integration services rely on docker images to do
their work, I think it would be useful to have an OSGeo docker
registry where OSGeo projects can push their images, using the OSGeo
Userid as authentication.
I've setup a private registry on my own host and started using it
for fetching build-test images for PostGIS, GEOS and Librttopo,
but my test setup doesn't use the OSGeo LDAP for authentication.
The space taken by my 4 docker images is currently 2.6G.
I guess it may grow easily, but space shouldn't be a big issue
these days, right ?
As we've been discussing about getting more disk space for
the "download" machine, can we take in account a possible
increase in disk space due to serving docker images too ?
Or should we just surrender to the centralization of docker hub ?
--strk;
I would do Docker Hub but not rule out our own at some point. Since
there are already many OSGeo things on Docker Hub it makes sense for us
to maintain an official section just like we do on Github.
Go ahead and get started on registering OSGeo with them, or is there
someone really into Docker that wants to take lead?
On Mon, Jul 25, 2016 at 12:33:34PM +0200, Mateusz Loskot wrote:
On 25 July 2016 at 12:14, Sandro Santilli <strk@kbt.io> wrote:
> As more and more services are distributed as docker images and most
> modern continuous integration services rely on docker images to do
> their work, I think it would be useful to have an OSGeo docker
> registry where OSGeo projects can push their images, using the OSGeo
> Userid as authentication.'
How it could be useful exactly?
To own the technology we rely upon, to use the existing OSGeo
Userid rather than having to create a new account.
Can you outline any use cases directly applicable to OSGeo
activities or projects?
Beside the need for a new account, the use cases I have in mind are all
also satisfiable by using hub.docker.io (the centralized service).
On Mon, Jul 25, 2016 at 08:31:15AM -0500, Howard Butler wrote:
> On Jul 25, 2016, at 6:12 AM, Tom Kralidis <tomkralidis@gmail.com> wrote:
> Given our limited and precious reosurces I would advocate for using Docker
> Hub with an OSGeo organization setup and have an internal setup for
> protected/sensitive/OSGeo Dockerfile's where required.
Me too, especially considering that every docker install will seamlessly consume images from DockerHub, and private repos require adding certificates -- which users can easily goof up.
You mean pulling an image from a custom registry would still
pull portions of it from DockerHub ? The "FROM xxxy" portion ?
I didn't get the certificates part. Letsencrypt makes setting up
certificates really easy.