[ https://issues.apache.org/jira/browse/YARN-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830578#comment-16830578 ]
Eric Yang commented on YARN-9523: --------------------------------- [~jeagles] With all due respect, this issue will not be committed unless there is consensus. I am working on Ozone, and the same discussion has surfaced in Ozone community. The suggestion came up to use dist profile to build docker image. It seems like a reasonable change to ensure that Hadoop community can build distro that includes docker images. I like to bring this up to bi-weekly YARN docker meeting for discussion again because multiple subprojects faces similar problem. It's best to solve this problem in consistent manner instead of having Ozone project build in kubernetes, HDFS in docker-compose, and YARN in docker. Without consistency, it impacts techniques that are used for integration tests. It would be best to talk about this option upfront. > Rename docker profile to dist profile > ------------------------------------- > > Key: YARN-9523 > URL: https://issues.apache.org/jira/browse/YARN-9523 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Eric Yang > Priority: Major > > It would be nice to make Application catalog docker image as part of the > distribution. The suggestion is to change from: > {code:java} > mvn clean package -Pnative,dist,docker{code} > to > {code:java} > mvn clean package -Pnative,dist{code} > User can still build tarball only using: > {code:java} > mvn clean package -DskipDocker -DskipTests -DskipShade -Pnative,dist{code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org