You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
We are running ibm-http-server:8.5.5.9 with docker 1.12.0 on a centos7x64 host.
We were experimenting with response files and looking at the /opt/IBM/WebSphere/Toolbox/WCT/wctcmd.sh script. It sets $JAVA_EXE as ../java/jre/bin/java
However, (output from inside the running container):
# pwd
/opt/IBM/WebSphere/Toolbox/java/jre/bin
# ./java -version
bash: ./java: No such file or directory
We were able to reproduce this on a developer macbook as well using the same image and docker 1.12.
In the past, we've noticed the /opt/IBM/WebSphere/Toolbox/java path was a symlink to /opt/IBM/HTTPServer/java (which continues to be a valid java installation).
I'm not sure why the discrepancy between the current image and images from several months ago (but same product version and image tag - 8.5.5.9).
Thank you for any feedback/input.
SJ
The text was updated successfully, but these errors were encountered:
I think the symlinks would be better to save space but currently the installation script simply installs IHS, Plugin and WCT with their own respective JDK (not even JRE) I can check to see if I can incorporate it into my fork.
Hi all,
We are running ibm-http-server:8.5.5.9 with docker 1.12.0 on a centos7x64 host.
We were experimenting with response files and looking at the /opt/IBM/WebSphere/Toolbox/WCT/wctcmd.sh script. It sets $JAVA_EXE as ../java/jre/bin/java
However, (output from inside the running container):
We were able to reproduce this on a developer macbook as well using the same image and docker 1.12.
In the past, we've noticed the /opt/IBM/WebSphere/Toolbox/java path was a symlink to /opt/IBM/HTTPServer/java (which continues to be a valid java installation).
I'm not sure why the discrepancy between the current image and images from several months ago (but same product version and image tag - 8.5.5.9).
Thank you for any feedback/input.
SJ
The text was updated successfully, but these errors were encountered: