atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2012) Docker - image & hub - for Atlas
Date Wed, 15 Nov 2017 06:18:00 GMT


Nigel Jones commented on ATLAS-2012:

Looking at docker hub, for an individual to upload an image is pretty simple.
However to allow multiple users (within the atlas community) to update the image would require
setting up an organization & then adding members

A number of projects though including zookeeper, flink, httpd, solr, storm have 'official'
images, guidelines for this are at More
review is required, but I think in the medium term this is what we should target, this comes
with it requirements around aspects like issue tracking

In order to get an image uploaded promptly, a pragmatic approach is probably to create an
organization (adding any individual interested) and upload as a contributed image in order
to learn/verify the process, and once we have something useful that meets the official requirements
to work towards migrating the image there.

> Docker - image & hub - for Atlas
> --------------------------------
>                 Key: ATLAS-2012
>                 URL:
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>             Fix For: 1.0.0
>         Attachments: ATLAS-2012-Build-docker-image.patch, atlas_docker.patch, atlas_docker1.patch,
> Docker is increasingly become a standard way of easily running components in a flexible
manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's appeal
> 1. We could provide a simple example of how to create a docker image from the Atlas build.
This could be published on the wiki & it would make it easier for developers to use Atlas
within a docker environment - mostly by addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build process. This
builds on #1 by automating the creation of the image & making it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub, making it near
trivial for any developer to easily pull down and experiment with Atlas. Full source of course
would be provided/documented so that a user could customize as needed for their environment
plus of course improve what is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts in other
teams to easily work together & be orchestrated 

This message was sent by Atlassian JIRA

View raw message