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

ASF GitHub Bot commented on HADOOP-18682:
-----------------------------------------

xBis7 commented on PR #6483:
URL: https://github.com/apache/hadoop/pull/6483#issuecomment-1923724996

   @ayushtkn Thanks for the review.
   
   > I think Ozone even builds the docker images during:
   
   BTW, that's where I got the idea for this PR.
   
   > because we are doing stuff for docker image, not sure how much, we need to 
see the time diff with & without the patch....
   
   The times I posted above, are for this branch. Let me get the times for 
trunk as well and post them in another comment.
   
   Because we are mounting the dist directory as a docker volume for the 
containers, there isn't any extra time needed in the build other than the time 
we spend building the dist directory. It's not building an official hadoop 
image using a Dockerfile.
   




> Move hadoop docker scripts under the main source code
> -----------------------------------------------------
>
>                 Key: HADOOP-18682
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18682
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Ayush Saxena
>            Assignee: Christos Bisias
>            Priority: Major
>              Labels: pull-request-available
>
> Exploratory:
> Coming from https://github.com/apache/hadoop/pull/5514
> We have docker scripts maintained in a different branch. We can explore them 
> to have as part of dev-support in our main source code.
> They can be used for new users to try the code without the headache of 
> building and doing crazy stuff, and can help in dev testing as well



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to