adoroszlai commented on PR #23:
URL: 
https://github.com/apache/ozone-docker-runner/pull/23#issuecomment-2223930222

   Thanks @LZD-PratyushBhatt for updating the patch.
   
   Secure tests are still failing.  I was wrong, the problem is not with `kdc`. 
 `kdc` is able to start; `scm` and other containers fail with:
   
   ```
   ERROR: JAVA_HOME /usr/lib/jvm/jre does not exist.
   ```
   
   Some tests (mostly the `ozonesecure*` ones) in Ozone 1.4.0 and earlier set 
`JAVA_HOME=/usr/lib/jvm/jre`, overriding actual Java location in the image.  
Since we cannot change earlier Ozone release bits, we need to add another 
symlink in the image:
   
   ```
   RUN mkdir -p /usr/lib/jvm && ln -s $JAVA_HOME /usr/lib/jvm/jre # 
compatibility with Ozone 1.4.0 and earlier compose env.
   ```
   
   right below:
   
   
https://github.com/apache/ozone-docker-runner/blob/75aee6aef8109d1097b003c09d8263962d4b511d/Dockerfile#L166
   
   or anywhere after that.


-- 
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