-
-
Notifications
You must be signed in to change notification settings - Fork 218
Description
As of December 20th 2022 the openJDK images from the docker library were deprecated (see docker-library/openjdk@d2f1e2d and docker-library/openjdk#505). With this comes with a handful of questions for continuation of the reposilite docker images. Below are some choices to go with moving forward.
One base image to rule them all
Pick a new single base image for future reposilite images
- Amazon's Corretto JVM images
amazoncorretto:${JDK}-al2023based off of Amazon Linux 2023amazoncorretto:${JDK}-alpinebased off Alpine Linux
- Eclipse's Temurin JVM images
eclipse-temurin:${JDK}based off Ubuntueclipse-temurin:${JDK}-alpinebased off Alpine Linuxeclipse-temurin:${JDK}-windowsservercorebased off Windows Server 2016 (I advise against this one)
- BellSoft Liberica JVM images
bellsoft/liberica-runtime-container:jre-${JDK}
- IBM Semeru (OpenJ9) JVM images
ibm-semeru-runtimes:open-${JDK}based off Ubuntu
- SapMachine JVM images
sapmachine:${JDK}based off Ubuntu
With one of these images rework the Dockerfile to use said image.
Example
How about all of them
Publish a build for x amount of base runtime images using artifacts from a build image. Allowing users to choose their preferred JVM runtime to run their repo with. A method of doing this could be using docker buildx bake to make a build job to build the JAR file and cache them for building the runtime images (which could be done in parallel).
More commentary is wanted or more potential solutions. Many thanks.