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

Amir Sanjar commented on HADOOP-13329:
--------------------------------------

> - I agree with your statement that Dockerfiles would get moved to x86_64, 
> ppc64le, ARM64 or whatever.
> - I understand your concern, however Ubuntu 15.04 public repository does not 
> house protobuf v2.5 any more. As an ex-canonical and Ubuntu developer I 
> assure you https://launchpad.net/ubuntu/+source/protobuf/2.5.0-9ubuntu1/ 
> launchpad is long lasting. There are repos with protobuf 2.5 for Power, but 
> security was my main concern.
> - Why the custom code for leveldb? leveldb in public maven repository has x86 
> specif could that breaks on Power and ARM :( In meanwhile we are working with 
> Maven community to establish a "secure" maven Power repo.
> - Interesting idea, I agree with your statement "We should probably rework 
> the start-build-env.sh docker call to avoid having two copies of the 
> hadoop-env-checks script. We could have it copy the correct Dockerfile and 
> the hadoop-env-checks script to some place under target or patchprocess and 
> build it from there." 
> - Regarding Apache Yetus, we are working on it.. 
 

> Dockerfile doesn't work on Linux/ppc
> ------------------------------------
>
>                 Key: HADOOP-13329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13329
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Allen Wittenauer
>            Assignee: Amir Sanjar
>         Attachments: HADOOP-13329.patch
>
>
> We need to rework how the Dockerfile is built to support both Linux/x86 and 
> Linux/PowerPC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to