6u41-jdk-centos,6u41-centos,6-jdk-centos,6-centos(6-jdk/centos/Dockerfile)6u41-jre-centos,6-jre-centos(6-jre/centos/Dockerfile)7u161-jdk-centos,7u161-centos,7-jdk-centos,7-centos(7-jdk/centos/Dockerfile)7u161-jre-centos,7-jre-centos(7-jre/centos/Dockerfile)8u151-jdk-centos,8u151-centos,8-jdk-centos,8-centos,jdk-centos,centos(8-jdk/centos/Dockerfile)8u151-jre-centos,8-jre-centos,jre-centos(8-jre/centos/Dockerfile)
An extension of the official openjdk image with extra OS variants.
This image shares all its features with the official openjdk image.
The openjdk images come in different flavors, each designed for a specific use case.
This image is based on the CentOS operating system, available in the centos official image.
A tagging convention determines the version of the components distributed with the openjdk image.
- OpenJDK release: α
- JRE (Java Runtime Environment) only
- OpenJDK release: α
- JDK (Java Development Kit) + JRE
You can automatically update OpenJDK versions and regenerate the repository tree with:
./generate-dockerfiles.sh
After committing changes to the repository, regenerate the library definition file with:
./generate-bashbrew-library.sh >| openjdk
All images in this repository can be rebuilt and tagged manually using Bashbrew, the tool used for cloning, building, tagging, and pushing the Docker official images. To do so, simply call the bashbrew utility, pointing it to the included openjdk definition file as in the example below:
bashbrew --library . build openjdk
Any push to the upstream centos repository or to the source repository triggers an automatic rebuild of all the images in this repository. From a high perspective the automated build pipeline looks like the below diagram:
