[
https://issues.apache.org/jira/browse/HADOOP-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579023#comment-17579023
]
Veli-Jussi Raitila edited comment on HADOOP-18401 at 8/12/22 6:09 PM:
----------------------------------------------------------------------
And subsequently, I do not know why the Dockerfile and Dockerfile_aarch64 are
so different in the first place, but commenting out the line
{noformat}
RUN pip3 install pylint==2.6.0 python-dateutil==2.8.1{noformat}
for the ARM Dockerfile does then allow the container to start.
However, I think the root cause is in the packaging of the lazy-object-proxy
library and submitted a bug report
[here|https://github.com/ionelmc/python-lazy-object-proxy/issues/69].
was (Author: JIRAUSER294345):
And subsequently, I do not know why the Dockerfile and Dockerfile_aarch64 are
so different in the first place, but commenting out the line
{noformat}
RUN pip3 install pylint==2.6.0 python-dateutil==2.8.1{noformat}
for the ARM Dockerfile does then allow the container to start.
However, I think the root cause is in the packaging of the lazy-object-proxy
library and submitted a bug report [here|http://example.com].
> release files miss hadoop-3.3.4-aarch64.tar.gz
> ----------------------------------------------
>
> Key: HADOOP-18401
> URL: https://issues.apache.org/jira/browse/HADOOP-18401
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.3.2, 3.3.3, 3.3.4
> Reporter: Ling Xu
> Priority: Minor
> Attachments: image-2022-08-11-14-54-15-490.png
>
>
> release files miss hadoop-3.3.4-aarch64.tar.gz
> !image-2022-08-11-14-54-15-490.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
