-
Notifications
You must be signed in to change notification settings - Fork 477
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
JAVA8 Alpine JRE and JDK image tags are broken since last update #285
Comments
Are you referring to the |
I am referring to OpenJDK tags. |
This might help with seeing the layout of OpenJDK 11 doesn't have Alpine support #212 (comment) $ docker pull openjdk:13-alpine
13-alpine: Pulling from library/openjdk
Digest: sha256:3a99d04ea2b4114b57e710cab2560ed86d0629b241a77dea60f0df57704818d8
Status: Downloaded newer image for openjdk:13-alpine Since OpenJDK 11+ is from Oracle; there aren't JRE versions, just JDK. But for 11 we still have the JRE variant which isn't from Oracle As for your specific error |
Here is the example Dockerfile for reference where we are getting error "/bin/sh: /app/start.sh: not found"
|
If the shebang of your "start.sh" script is bash, that's a common cause of
that error (the Alpine images don't include Bash).
|
Closing since this doesn't seem to be an issue with the image If you have further questions you could try asking the Docker Community Forums, the Docker Community Slack, or Stack Overflow. Since these repositories are for issues with the image and not necessarily for questions of usability |
Thanks for your reply and indeed start.sh script was having bash. |
Another question, does 8-jre-alpine docker tag is deprecated for openjdk:jre-alpine? |
Hi Team,
We are seeing below errors for JAVA8 Alpine JRE and JDK image tags.
/bin/sh: /app/start.sh: not found
Can you please look into this?
We have also noticed that jre-alpine tag is no more supported but still exist. Is there any plan to stop supporting this tag in future and should use version specific tags only like 8-jre-alpine
The text was updated successfully, but these errors were encountered: