[
https://issues.apache.org/jira/browse/HADOOP-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071773#comment-18071773
]
ASF GitHub Bot commented on HADOOP-19814:
-----------------------------------------
cnauroth commented on code in PR #8408:
URL: https://github.com/apache/hadoop/pull/8408#discussion_r3040702841
##########
Dockerfile:
##########
@@ -14,7 +14,7 @@
# limitations under the License.
FROM apache/hadoop-runner
Review Comment:
I'm thinking what we need to do is:
1. Release a new
~~apache/hadoop-runner:jdk17-u2204~~apache/hadoop-runner:jdk17-u2404 that
aligns the OS with the release container like Cheng suggested.
2. Additionally, the base container needs another change to set ownership of
/opt to the hadoop user so that it has permission to install the Hadoop bits.
[This
line](https://github.com/apache/hadoop/blob/docker-hadoop-runner-latest/Dockerfile#L35)
in apache/hadoop-runner:latest is missing from
[apache/hadoop-runner:jdk17-u2204](https://github.com/apache/hadoop/blob/docker-hadoop-runner-jdk17-u2204/Dockerfile).
Actually these 2 images are quite different. I wonder if they should be more
aligned.
3. Create a new docker-hadoop-3.5 branch that uses the new
apache/hadoop-runner:jdk17-u2204 for the base image. This way, we'll be able to
independently release images for new 3.4 and 3.5 releases.
I'll proceed with this approach in a little while unless others have
feedback.
> Release Apache Hadoop 3.5.0
> ---------------------------
>
> Key: HADOOP-19814
> URL: https://issues.apache.org/jira/browse/HADOOP-19814
> Project: Hadoop Common
> Issue Type: Task
> Components: build
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Release tracking for Hadoop 3.5.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
