Estimated reading time: 6 minutes

Official IBM® SDK, Java™ Technology Edition Docker Image.

GitHub repo:

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Store page for this image at

Supported tags and respective Dockerfile links

Quick reference


The images in this repository contain IBM® SDK, Java™ Technology Edition, version 1.8.0_sr4fp10 (8.0-4.10) and 1.9.0_ea2 (9.0 early access). For Java 8 images, see what’s new. See the license section for restrictions that relate to the use of this image. For more information about IBM® SDK, Java™ Technology Edition and API documentation, see the IBM Knowledge Center. For tutorials, recipes, and Java usage in Bluemix, see IBM developerWorks.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Java 9 Beta

Java 9 Beta Images are now available for you to test and provide feedback ! Please see the Open Beta Community page for more details. The images are available for all three supported architectures (x86_64, s390x and ppc64le). Currently the images only have the SDK (Software Developers Kit).


There are three types of Docker images here: the Software Developers Kit (SDK), and the Java Runtime Environment (JRE) and a small footprint version of the JRE (SFJ). These images can be used as the basis for custom built images for running your applications.

Small Footprint JRE

The Small Footprint JRE (SFJ) is designed specifically for web developers who want to develop and deploy cloud-based Java applications. Java tools and functions that are not required in the cloud environment, such as the Java control panel, are removed. The runtime environment is stripped down to provide core, essential function that has a greatly reduced disk and memory footprint.

Alpine Linux

Consider using Alpine Linux if you are concerned about the size of the overall image. Alpine Linux is a stripped down version of Linux that is based on musl libc and Busybox, resulting in a Docker image size of approximately 5 MB. Due to its extremely small size and reduced number of installed packages, it has a much smaller attack surface which improves security. However, because the IBM SDK has a dependency on gnu glibc, installing this library adds an extra 8 MB to the image size. The following table compares Docker Image sizes based on the JRE version 8.0-3.10.

Ubuntu Alpine Ubuntu Alpine
305 MB 184 MB 220 MB 101 MB

Note: Alpine Linux is not an officially supported operating system for IBM® SDK, Java™ Technology Edition.

Architectures Supported

Docker Images for the following architectures are now available:

How to use this Image

To run a pre-built jar file with the JRE image, use the following commands:

FROM ibmjava:jre
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]

To download the latest Java 9 Beta (Early Access) Image:

docker pull ibmjava:9-ea2-sdk
FROM ibmjava:jre
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]

You can build and run the Docker Image as shown in the following example:

docker build -t japp .
docker run -it --rm japp

If you want to place the jar file on the host file system instead of inside the container, you can mount the host path onto the container by using the following commands:

FROM ibmjava:jre
CMD ["java", "-jar", "/opt/app/japp.jar"]
docker build -t japp .
docker run -it -v /path/on/host/system/jars:/opt/app japp

Using the Class Data Sharing feature

IBM SDK, Java Technology Edition provides a feature called Class data sharing. This mechanism offers transparent and dynamic sharing of data between multiple Java virtual machines (JVMs) running on the same host thereby reducing the amount of physical memory consumed by each JVM instance. By providing partially verified classes and possibly pre-loaded classes in memory, this mechanism also improves the start up time of the JVM.

To enable class data sharing between JVMs that are running in different containers on the same host, a common location must be shared between containers. This requirement can be satisfied through the host or a data volume container. When enabled, class data sharing creates a named “class cache”, which is a memory-mapped file, at the common location. This feature is enabled by passing the -Xshareclasses option to the JVM as shown in the following Dockerfile example:

FROM ibmjava:jre
RUN mkdir /opt/shareclasses
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-Xshareclasses:cacheDir=/opt/shareclasses", "-jar", "/opt/app/japp.jar"]

The cacheDir sub-option specifies the location of the class cache. For example /opt/sharedclasses. When sharing through the host, a host path must be mounted onto the container at the location the JVM expects to find the class cache. For example:

docker build -t japp .
docker run -it -v /path/on/host/shareclasses/dir:/opt/shareclasses japp

When sharing through a data volume container, create a named data volume container that shares a volume.

docker create -v /opt/shareclasses --name classcache japp /bin/true

Then start your JVM container by using --volumes-from flag to mount the shared volume, as shown in the following example:

docker run -it --volumes-from classcache japp

See Also

See the Websphere-Liberty image, which builds on top of this IBM docker image for Java.


The Dockerfiles and associated scripts are licensed under the Apache License 2.0.

Licenses for the products installed within the images:

library, sample, ibmjava