[SAC] Running an osgeo docker registry

[Tom Kralidis]

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 at kbt.io>
> Reply-To: System Administration Committee Discussion/OSGeo
>     <sac at lists.osgeo.org>, sac at lists.osgeo.org,
>     Alex Mandel <tech at wildintellect.com>
> To: sac at 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 ?
>
> --strk;