[ 
https://issues.apache.org/jira/browse/KAFKA-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858076#comment-16858076
 ] 

ASF GitHub Bot commented on KAFKA-8499:
---------------------------------------

lbradstreet commented on pull request #6898: KAFKA-8499: ensure java is in PATH 
for ducker system tests
URL: https://github.com/apache/kafka/pull/6898
 
 
   openjdk:8/openjdk:11 used to include java and other java programs in 
/usr/bin. It has since been moved to /usr/local/openjdk-VERSION/bin, which will 
cause problems when the system tests invoke any java binary if the latest 
openjdk image has been pulled. The openjdk images have been updated with the 
same tag, so this can happen suddenly without any other code changes if the new 
version is pulled.
   
   The primary symptom is that ZooKeeper will fail to start due to java not 
being found when running the system tests in ducker.
   
   This PR allows PermitUserEnvironment, and sets the ducker user's 
`.ssh/environment` to include JAVA_HOME/bin in its path.
   
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Ducker missing java commands in path for ducker user on openjdk docker images
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-8499
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8499
>             Project: Kafka
>          Issue Type: Bug
>          Components: system tests
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Lucas Bradstreet
>            Priority: Major
>
> openjdk:8/openjdk:11 used to include java and other java programs in 
> /usr/bin. It has since been moved to /usr/local/openjdk-VERSION/bin, which 
> will cause problems when the system tests invoke any java related utility as 
> well as java itself if the user is using a later image with the same tag. The 
> openjdk images have been updated with the same tag, so this can happen 
> suddenly without any other code changes if the new version is pulled.
> The primary symptom on running the tests in ducker is that ZooKeeper will 
> fail to start due to java not being found.
> We need to ensure the ducker user that is created in the Dockerfile includes 
> the new location that java is installed to is included in its path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to