adoroszlai opened a new pull request, #4137:
URL: https://github.com/apache/ozone/pull/4137

   ## What changes were proposed in this pull request?
   
   `ozone-om-ha` uses a temporary Docker image based on top of the regular 
`ozone-runner` images.
   
   HDDS-6293 added support for custom `ozone-runner` image, but the change had 
a bug: `OZONE_RUNNER_IMAGE` variable was not passed to the Docker build context 
in `ozone-om-ha`.  This was not noticed as this test is disabled due to 
flakiness.
   
   Compare to `ozonescripts` environment, which also uses its own derived image.
   
   https://issues.apache.org/jira/browse/HDDS-7714
   
   ## How was this patch tested?
   
   ```
   $ cd hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-om-ha
   $ docker-compose up -d
   Building datanode
   Sending build context to Docker daemon  29.18kB
   Step 1/23 : ARG OZONE_RUNNER_IMAGE
   Step 2/23 : ARG OZONE_RUNNER_VERSION
   Step 3/23 : FROM ${OZONE_RUNNER_IMAGE}:${OZONE_RUNNER_VERSION}
    ---> 2f81b649e1b7
   Step 4/23 : RUN sudo yum install -y openssh-clients openssh-server
    ---> Running in 61a7cb57a64c
   ...
   Successfully built 9667608351f9
   Successfully tagged ozone-runner-om-ha:20220623-1
   WARNING: Image for service datanode was built because it did not already 
exist. To rebuild this image you must use `docker-compose build` or 
`docker-compose up --build`.
   Creating ozone-om-ha_om2_1      ... done
   Creating ozone-om-ha_scm_1      ... done
   Creating ozone-om-ha_om3_1      ... done
   Creating ozone-om-ha_om1_1      ... done
   Creating ozone-om-ha_datanode_1 ... done
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to