Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JDK8: JAVA_HOME and JDK folder name inside the docker image differs from image tag #32

Closed
neomatrix369 opened this issue Jun 23, 2018 · 4 comments
Labels

Comments

@neomatrix369
Copy link
Member

neomatrix369 commented Jun 23, 2018

While using image tag adoptopenjdk/openjdk8:jdk8u152-b16, I found that the folder name where the JAVA_HOME points to is called jdk8u144-b16 and not jdk8u152-b16

I have deleted the image from my local repo and rebuild the docker image and I still get it, also built it elsewhere and got the same issue.

$ whereis java
java: /opt/java/openjdk/jdk8u144-b01/bin/java

Temporarily I have set the folder name to jdk8u144-b16 - although JAVA_HOME does point to this folder.

$ echo $JAVA_HOME
/opt/java/openjdk/jdk8u144-b01

Basically, using image adoptopenjdk/openjdk8:jdk8u152-b16 still gives me jdk8u144-b16. Also there is no tag for version adoptopenjdk/openjdk8:jdk8u172 <== this is tag latest.

@neomatrix369 neomatrix369 changed the title JDK folder name inside the docker image differs from image tag JDK8: JAVA_HOME and JDK folder name inside the docker image differs from image tag Jun 23, 2018
@dinogun
Copy link
Collaborator

dinogun commented Jun 29, 2018

This is a problem with the build scripts as the dir created is different from the release name mentioned in the api. Should hopefully get fixed in the new build scripts.
fyi @johnoliver @karianna

@dinogun
Copy link
Collaborator

dinogun commented Jun 29, 2018

PR #33 temporarily fixes this by moving the JAVA_HOME to a static path (viz /opt/java/openjdk/)

@neomatrix369
Copy link
Member Author

@dinogun thanks for the update, they are in good hands. will await the scripts - best that way, a number of bugs will get swept away in the process.

@dinogun
Copy link
Collaborator

dinogun commented Jul 8, 2018

PR #33 is merged and have tested that this problem goes away.

@dinogun dinogun closed this as completed Jul 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants