[
https://issues.apache.org/jira/browse/HDDS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914629#comment-16914629
]
Elek, Marton commented on HDDS-2025:
------------------------------------
Official docker images are based on the official/voted releases. So it's not a
blocker for release (especially as it should be committed to
hadoop-docker-ozone repository).
1) create the release package + vote + upload
2) tag the hadoop-docker-ozone repository which will produce the apache/ozone
images
It's possible to test the image before the release (download a snapshot tar). I
did it today and didn't find any blocking problem which should be fixed in the
Hadoop repo. I have a small patch and will upload soon (to fix files in
hadoop-docker-ozone repo). But I would like to improve the wiki pages to write
down:
* What should be done during (=after) the release process
* How can it be tested right now.
> Update the Dockerfile of the official apache/ozone image
> --------------------------------------------------------
>
> Key: HDDS-2025
> URL: https://issues.apache.org/jira/browse/HDDS-2025
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
>
> The hadoop-docker-ozone repository contains the definition of the
> apache/ozone image.
> https://github.com/apache/hadoop-docker-ozone/tree/ozone-latest
> It creates a docker packaging for the voted and released artifact, therefore
> it can be released after the final vote.
> Since the latest release we did some modification in our Dockerfiles. We need
> to apply the changes to the official image as well. Especially:
> 1. use ozone-runner as a base image instead of hadoop-runner
> 2. rename ozoneManager service to om as we did everywhere
> 3. Adjust the starter location (the script is moved to the released tar file)
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
