Thanks Eric the suggestions. Unfortunately (as Anu wrote it) our use-case is slightly different.
It was discussed in HADOOP-14898 and HDDS-851 but let me summarize the motivation: We would like to upload containers to the dockerhub for each releases (eg: apache/hadoop:3.2.0) According to the Apache release policy, it's not allowed, to publish snapshot builds (=not voted by PMC) outside of the developer community. 1. We started to follow the pattern which is used by other Apache projects: docker containers are just different packaging of the already voted binary releases. Therefore we create the containers from the voted releases. (See [1] as an example) 2. With separating the build of the source code and the docker image we get additional benefits: for example we can rebuild the images in case of a security problem in the underlying container OS. This is just a new empty commit on the branch and the original release will be repackaged. 3. Technically it would be possible to add the Dockerfile to the source tree and publish the docker image together with the release by the release manager but it's also problematic: a) there is no easy way to stage the images for the vote b) we have no access to the apache dockerhub credentials c) it couldn't be flagged as automated on dockerhub d) It couldn't support the critical updates as I wrote in (2.). So the easy way what we found is ask INFRA to register a branch to the dockerhub to use for the image creation. The build/packaging will be done by the dockerhub but only released artifacts will be included. Because the limitation of the dockerhub to set a map between branch names and tags, we need a new repository instead of the branch (see the comments in HDDS-851 for more details). We also have a different use case to build developer images to create a test cluster. These images will never be uploaded to the hub. We have a Dokcerfile in the source tree for this use case (see HDDS-872). And thank you very much the hint, I will definitely check how YARN-7129 can do it and will try to learn from it. Thanks, Marton [1]: https://github.com/apache/hadoop/tree/docker-hadoop-3 On 1/30/19 2:50 AM, Anu Engineer wrote: > Marton please correct me I am wrong, but I believe that without this branch > it is hard for us to push to Apache DockerHub. This allows for Apache account > integration and dockerHub. > Does YARN publish to the Docker Hub via Apache account? > > > Thanks > Anu > > > On 1/29/19, 4:54 PM, "Eric Yang" <ey...@hortonworks.com> wrote: > > By separating Hadoop docker related build into a separate git repository > have some slippery slope. It is harder to synchronize the changes between > two separate source trees. There is multi-steps process to build jar, > tarball, and docker images. This might be problematic to reproduce. > > It would be best to arrange code such that docker image build process can > be invoked as part of maven build process. The profile is activated only if > docker is installed and running on the environment. This allows to produce > jar, tarball, and docker images all at once without hindering existing build > procedure. > > YARN-7129 is one of the examples that making a subproject in YARN to > build a docker image that can run in YARN. It automatically detects presence > of docker and build docker image when docker is available. If docker is not > running, the subproject skips and proceed to next sub-project. Please try > out YARN-7129 style of build process, and see this is a possible solution to > solve docker image generation issue? Thanks > > Regards, > Eric > > On 1/29/19, 3:44 PM, "Arpit Agarwal" <aagar...@cloudera.com.INVALID> > wrote: > > I’ve requested a new repo hadoop-docker-ozone.git in gitbox. > > > > On Jan 22, 2019, at 4:59 AM, Elek, Marton <e...@apache.org> wrote: > > > > > > > > TLDR; > > > > I proposed to create a separated git repository for ozone docker > images > > in HDDS-851 (hadoop-docker-ozone.git) > > > > If there is no objections in the next 3 days I will ask an Apache > Member > > to create the repository. > > > > > > > > > > LONG VERSION: > > > > In HADOOP-14898 multiple docker containers and helper scripts are > > created for Hadoop. > > > > The main goal was to: > > > > 1.) help the development with easy-to-use docker images > > 2.) provide official hadoop images to make it easy to test new > features > > > > As of now we have: > > > > - apache/hadoop-runner image (which contains the required dependency > > but no hadoop) > > - apache/hadoop:2 and apache/hadoop:3 images (to try out latest > hadoop > > from 2/3 lines) > > > > The base image to run hadoop (apache/hadoop-runner) is also heavily > used > > for Ozone distribution/development. > > > > The Ozone distribution contains docker-compose based cluster > definitions > > to start various type of clusters and scripts to do smoketesting. > (See > > HADOOP-16063 for more details). > > > > Note: I personally believe that these definitions help a lot to > start > > different type of clusters. For example it could be tricky to try > out > > router based federation as it requires multiple HA clusters. But > with a > > simple docker-compose definition [1] it could be started under 3 > > minutes. (HADOOP-16063 is about creating these definitions for > various > > hdfs/yarn use cases) > > > > As of now we have dedicated branches in the hadoop git repository > for > > the docker images (docker-hadoop-runner, docker-hadoop-2, > > docker-hadoop-3). It turns out that a separated repository would be > more > > effective as the dockerhub can use only full branch names as tags. > > > > We would like to provide ozone docker images to make the evaluation > as > > easy as 'docker run -d apache/hadoop-ozone:0.3.0', therefore in > HDDS-851 > > we agreed to create a separated repository for the hadoop-ozone > docker > > images. > > > > If this approach works well we can also move out the existing > > docker-hadoop-2/docker-hadoop-3/docker-hadoop-runner branches from > > hadoop.git to an other separated hadoop-docker.git repository) > > > > Please let me know if you have any comments, > > > > Thanks, > > Marton > > > > 1: see > > > https://github.com/flokkr/runtime-compose/tree/master/hdfs/routerfeder > > as an example > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
