[ 
https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849387#comment-16849387
 ] 

Elek, Marton commented on HADOOP-16092:
---------------------------------------

bq. The current user experience has been a very poor one. There are a lot of 
people using Hadoop images on Docker Hub. Some images has over 5 million use, 
but very few people use Hadoop-runner image

Please don't mix the two things. Usability and popularity are two different 
things. 

bq.  This should be enough to point out the current model is a non-starter for 
most people.

No. This shows the *popularity* of our *developer* image. 

bq.  Binary must be in docker image for production usage, which has been 
documented in docker-compose website.

100% agree:

*  apache/hadoop-runner --> this is for development and POC. This is just a 
*base* image. No ozone/hadoop inside
* apache/hadoop --> this is the real product image. Yes, it contains hadoop 
binary.

> Move the source of hadoop/ozone containers to the same repository
> -----------------------------------------------------------------
>
>                 Key: HADOOP-16092
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16092
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Gabor Bota
>            Priority: Major
>
> This is proposed by [~eyang] in 
> [this|https://lists.apache.org/thread.html/33ac54bdeacb4beb023ebd452464603aaffa095bd104cb43c22f484e@%3Chdfs-dev.hadoop.apache.org%3E]
>  mailing thread.
> bq. Hadoop community can decide what is best for Hadoop.  My preference is to 
> remove ozone from source tree naming, if Ozone is intended to be subproject 
> of Hadoop for long period of time.  This enables Hadoop community to host 
> docker images for various subproject without having to check out several 
> source tree to trigger a grand build
> As of now the source of  hadoop docker images are stored in the hadoop git 
> repository (docker-* branches) for hadoop and in hadoop-docker-ozone git 
> repository for ozone (all branches).
> As it's discussed in HDDS-851 the biggest challenge to solve here is the 
> mapping between git branches and dockerhub tags. It's not possible to use the 
> captured part of a github branch.
> For example it's not possible to define a rule to build all the ozone-(.*) 
> branches and use a tag $1 for it. Without this support we need to create a 
> new mapping for all the releases manually (with the help of the INFRA).
> Note: HADOOP-16091 can solve this problem as it doesn't require branch 
> mapping any more.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to