Hi t.bohn,
Short version:
Pull the atlassian/jira-*:* image you want to use again, you should find it's now shipping Java 232!
Long version:
As we build images for new product releases we will build from the latest base images. Right now, products that have shipped a release since the base images were updated will ship Java 232:
$ docker run --rm -it atlassian/confluence-server:latest java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)
Jira hasn't shipped a new release in between then and now, so the next version to be published will ship it automatically.
Older versions are not rebuilt automatically, but only under the following conditions:
- When we make changes to the underlying template (fixing a bug or adding a feature)
- When we manually trigger a rebuild of all images, e.g. in response to a CVE
That being the case I've manually triggered a rebuild, which has since completed. You should now be able to pull whichever Jira image tag you're using, and it will be running Java 232.
Let us know how you go!
Cheers,
Dave
Hi t.bohn,
Thanks for the report. After some discussion we've changed the default images to use the full version of the JDK. If you pull the latest versions they should now work,
Cheers,
Steve