library/ibmjavaMaintained by:
IBM Runtime Technologies
Where to get help:
the developerWorks forum for IBM Java Runtimes and SDKs
Dockerfile links8-jre, jre, 8, latest
8-sfj, sfj
8-sdk, sdk
Where to file issues:
GitHub; for troubleshooting, see our How Do I ...? page
Supported architectures: (more info)
amd64, ppc64le, s390x
Published image artifact details:
repo-info repo's repos/ibmjava/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/ibmjava label
official-images repo's library/ibmjava file (history)
Source of this description:
docs repo's ibmjava/ directory (history)
The images in this repository contain IBM® SDK, Java™ Technology Edition. For more information on the latest version and what's new, see sdk8 on IBM developerWorks and jdk11 on IBM developerWorks. 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 as well as tutorials, recipes, and Java usage in IBM Cloud, see IBM developerWorks.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Eclipse OpenJ9 is a high performance, scalable, Java virtual machine (JVM) implementation that represents hundreds of person-years of effort. Contributed to the Eclipse project by IBM, the OpenJ9 JVM underpins the IBM SDK, Java Technology Edition product that is a core component of many IBM Enterprise software products. Continued development of OpenJ9 at the Eclipse foundation ensures wider collaboration, fresh innovation, and the opportunity to influence the development of OpenJ9 for the next generation of Java applications. The Eclipse OpenJ9 Docker images are available through AdoptOpenJDK. They are available from here.
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 *** surface which improves security. IBM SDK has a dependency on gnu glibc, the sources can be found here. 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.
| JRE | JRE | SFJ | SFJ |
|---|---|---|---|
| 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.
Multi-Arch Image
Docker Images for the following architectures are now available:
ibmjava now has multi-arch support and so the exact same commands as below works on all supported architectures. This also means that it is no longer necessary to prefix the arch with the image name as that happens auto-magically.
To run a pre-built jar file with the JRE image, use the following commands:
dockerfileFROM 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:
consoledocker 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:
dockerfileFROM ibmjava:jre CMD ["java", "-jar", "/opt/app/japp.jar"]
consoledocker build -t japp . docker run -it -v /path/on/host/system/jars:/opt/app japp
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:
dockerfileFROM 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:
consoledocker 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.
consoledocker 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:
consoledocker run -it --volumes-from classcache japp
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:
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's ibmjava/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务