Skip to content

Add Azul Zulu images#2320

Open
FDelporte wants to merge 20 commits intodocker-library:masterfrom
FDelporte:feature/add_zulu
Open

Add Azul Zulu images#2320
FDelporte wants to merge 20 commits intodocker-library:masterfrom
FDelporte:feature/add_zulu

Conversation

@FDelporte
Copy link

@FDelporte FDelporte commented May 5, 2023

Proposal to add the Azul Zulu images as official images.

Relates to docker-library/official-images#14593
Relates to docker-library/official-images#16141

Copy link
Contributor

@whalelines whalelines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latest docker-library PR, docker-library/official-images#16141, appears to be adding azul-zulu, so the path of these files should be updated from zulu/ to azul-zulu/.

Comment on lines +16 to +35
* Azul Zulu 17 based on Ubuntu:
```
docker run -it --rm azul/azul-zulu:17 java -version
```
* Azul Zulu 17 based on Debian:
```
docker run -it --rm azul/azul-zulu-debian:17 java -version
```
* Azul Zulu 17 based on CentOS:
```
docker run -it --rm azul/azul-zulu-centos:17 java -version
```
* Azul Zulu 17 based on Alpine:
```
docker run -it --rm azul/azul-zulu-alpine:17 java -version
```
* Azul Zulu 17 based on Distroless:
```
docker run -it --rm azul/azul-zulu-distroless:17 --version
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These commands still all reference non-existent images. The PR to create a new DOI, docker-library/official-images#14593 , would create the images in the repository azul-zulu-openjdk, so the images would look something like azul-zulu-openjdk:17-ubuntu, i.e., there is no namespace and the base image type appears in the tag, not the repository.

Copy link
Author

@FDelporte FDelporte Feb 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct @whalelines, I modified this pull request to align with DOI merge request docker-library/official-images#16141.

But this means both pull requests should get approved and published together?

FYI as mentioned in the last comment in docker-library/official-images#14593, the correct merge request for DOI Azul Zulu is docker-library/official-images#16141

@geertjanw
Copy link

great, thank you, and can you also merge it, @LaurentGoderre?

@tianon
Copy link
Member

tianon commented May 17, 2024

Your continued patience is appreciated.

@FDelporte
Copy link
Author

This documentation proposal has been updated to align with the pull request Add Zulu Images from Azul systems in official-images:
docker-library/official-images#16141 (comment)

Copy link
Member

@yosifkit yosifkit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple comments/questions.

Copilot AI review requested due to automatic review settings March 3, 2026 08:04

This comment was marked as abuse.

Copy link
Member

@yosifkit yosifkit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.


Side note:
With all the extra commits in your branch, and our use of squash-and-merge in GitHub, it'll likely cause your branch to continue to grow with more Merge branch 'docker-library:master' into [branch] commits along with your past commits that were squash & merged. You'll likely want to rebase your branch on docker-library/docs/master (or just start a new branch from docker-library/docs/master each time you make a PR).

Some helpful links:

Comment on lines +11 to +40
## Azul Zulu Images

Azul Zulu images on Docker Hub are available for different combinations of versions, packages, and systems.

### Versions

The following Long Term Support (LTS) versions are available:

- 8
- 11
- 17
- 21
- 25

Short Term Support (STS) versions are available for six months after their initial release.

### Packages

The following package types are available:

- jdk (default)
- jdk-headless
- jre
- jre-headless

### Systems

Images based on the following base systems are available:

- Debian (apt)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of such a verbose set of lists that then have to be maintained over time, what do you think about describing the tag scheme/methodology here? (IMO it's already pretty obvious from the tags, but I might be skewed from looking at this kind of thing all day every day 😂)

Using Azul Zulu based on Debian:

```bash
docker run -it --rm azul-zulu:<ZULU_VERSION>-debian<DISTRO_VERSION> java -version
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
docker run -it --rm azul-zulu:<ZULU_VERSION>-debian<DISTRO_VERSION> java -version
docker run -it --rm %%IMAGE%%:<ZULU_VERSION>-debian<DISTRO_VERSION> java -version

Comment on lines +59 to +61
FROM azul-zulu:<VERSION>
RUN mkdir /opt/my-app
COPY my-app.jar /opt/my-app
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
FROM azul-zulu:<VERSION>
RUN mkdir /opt/my-app
COPY my-app.jar /opt/my-app
FROM %%IMAGE%%:<VERSION>
COPY my-app.jar /opt/my-app/

@@ -0,0 +1 @@
https://github.com/AzulSystems/azul-zulu-images/issues
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default for this file with be very similar to this (the ?q= on the end of the link here makes it show all issues by default, even closed, so you're less likely to get duplicates of recently closed issues):

[%%GITHUB-REPO%%/issues](%%GITHUB-REPO%%/issues?q=)

(so this file should be removed completely)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as an FYI, our tooling also supports a logo.svg here, if you wanted to make sure we always have enough fidelity if Docker Hub ever updates the logo resolution they support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants