adoptium /containers
Repo containing the dockerfiles and scripts to produce the official eclipse-temurin containers.
★ 302⑂ 130👁 19⑃ 877● 240▤ 0
+0
日增长
302
stars
130
forks
19
watchers
877
prs
240
issues
0
releases
README
Containers This repository contains the Dockerfiles for the official Adoptium images of the Eclipse Temurin distribution (OpenJDK). These images are made available in Docker Hub. If you are looking for the usage README then please head to the Official Docker Hub Documentation. Supported Images In general, we support Alpine, UBI, Ubuntu and Windows containers. List of Supported Images By Tag We maintain images for all LTS Java releases and the latest feature release. Older non-LTS releases are EOL and are removed from this repository and future Docker Hub manifests. Update Policy As these are official Docker Hub images, Docker Inc maintains the base image and so any critical CVEs in the base O/S layer gets updated by them in short order. Note that the eclipse-temurin images include openssl as a prerequisite of the wget and ca-certificates packages but they are NOT included in the Ubuntu base image so updates to openssl will not necessarily trigger an rebuild to pick up fixes. In general, low severity vulnerabilities can wait until the next rebuild. See this comment for some details and also the docker-library FAQ. The Debian and Ubuntu images are generally also built periodically (about once a month) and may also be triggered by dockerhub if another high security vulnerability is detected, such as in openssl. Adoptium has no mechanism - other than putting an update to the Dockerfiles - to explicitly trigger a rebuild at dockerhub. For JDK version updates, we update the dockerfiles and release on a quarterly cadence Temurin releases a Patch Set Update (PSU). Maintenance of Dockerfiles This section is for maintainers of the containers repository. Hourly automated Job A Updater GitHub Action runs every 30 mins which triggers the ./generate_dockerfiles.py script to update the Dockerfiles by creating a Pull Request containing any changes. It uses the jinja templates defined in docker_templates to generate the docker updates. It uses the Adoptium API to fetch the latest artefacts for each release. Manual Release Generally this is not necessary but during a release you can also trigger the above process by running ./generate_dockerfiles.py manually by heading to The GitHub Action definition and clicking the Run Workflow button and making sure the main (default) branch is selected, then click the next Run Workflow button. Review and Merge PR Once the PR from the hourly automated job is created you should review it (which itself tests all of the Docker Images that we have generate configuration for). Update Official Docker Hub Manifest Once you've merged the PR, you can update the official Docker Hub manifest. This is done by running the following command in the containers repo on your local machine: bash Get the latest changes git fetch --all Checkout the main branch git checkout main python3 dockerhub_doc_config_update.py This script will create a file called _eclipse-temurin_ by default. At the end it prints a pub
Top issues
#612[Bug]: Importing Ca certificates with USE_SYSTEM_CA_CERTS is slower than it used to be15 comments · 2024-07-24#497[Bug]: Maven in Alpine-Image not working (ClassNotFoundException)12 comments · 2024-02-02#688Error when try to start image9 comments · 2024-10-28#843EPIC: Provide Eclipse Temurin images on multiple registries7 comments · 2025-11-04#294Docker with Apache Ignite crash 1.8.0_332-b096 comments · 2022-10-20#556Update documentation for CA certificate support changes5 comments · 2024-05-09#754How to perform provenance attestation on these images ?4 comments · 2025-04-10#853Determine naming conventions for non-dockerhub container pushes3 comments · 2025-11-24