Run Azul Zulu in a Docker Container

Run Java Apps With Zulu CA in Docker

You can test the Docker image by running the following command in a terminal:

 
docker run -it --rm azul/zulu-openjdk:21 java -version

The command allocates a terminal and runs java. It prints a message similar to this:

 
openjdk version "21.0.4" 2024-07-16 LTS
OpenJDK Runtime Environment Zulu21.36+17-CA (build 21.0.4+7-LTS)
OpenJDK 64-Bit Server VM Zulu21.36+17-CA (build 21.0.4+7-LTS, mixed mode, sharing)

If you see this message in your terminal, you’ve successfully executed java inside a container.

The command above simply executes java. To run a Java application, you must provide your application classes and resources to the java command. You do this by mounting a local directory from the container.

As an example, let’s assume that your application files are located in a single directory. You would normally run the app by executing java MyApp in that directory. Use the -v option of docker run to make the directory available inside the container. The command might look like this:

 
docker run -it --rm \
    -v ${PWD}:/usr/src/project  \
    -e CLASSPATH=/usr/src/project \
    azul/zulu-openjdk:11 java MyApp

Manage Access Tokens

Customers can manage their user token using the Azul token management app on access.azul.com. You need to login with the same credentials used for ftp.azul.com. These tokens can be used in combination with the ftp username to create the basic authentication header required to download from the restricted repositories.

In the examples below, the following references are used:

Please contact the Azul Support team ([email protected]) if you need assistance with your tokens.

Create Docker Image with SA Zulu

Tagging Scheme for SA Images

Each Docker image is tagged using a versioned and alias-based scheme that reflects the underlying Java release, Zulu build, and runtime variant (JDK or JRE). The underlying architecture is not exposed in the tag. All published tags reference multi-architecture images, supporting both amd64 and arm64 transparently.