ubuntu/jreCurrent jre Docker Image from Canonical, based on Ubuntu. Receives security updates and rolls to newer jre or Ubuntu release. This repository is free to use and exempted from per-user rate limits.
This image packs the Java Runtime Environment, coming from the OpenJDK project, a free and open source implementation of the Java Platform, Standard Edition (Java SE). OpenJDK is the official reference implementation of Java SE since version 7. Read more. Java is a registered trademark of Oracle and/or its affiliates.
This image does not include bash nor a package manager nor the OpenJDK. Its purpose is to serve as a runtime, final-stage base image for compatible Java applications.
Read more about ***led Ubuntu for OpenJDK JRE, a new class of OCI images, on the Ubuntu blog. And remember, the best base image is FROM scratch: so you could also easily craft your own ***led Ubuntu base for your app specific needs.
Please note that the Ubuntu 22.04 JRE images are Dockerfile-base images, whereas from Ubuntu 24.04 onward the images are now rocks. As such the entrypoint is now Pebble. Read more on the Rockcraft docs.
Ubuntu 22.04 JRE images have java as the entrypoint.
bash$ docker run --rm ubuntu/jre:17_edge Usage: java [options] <mainclass> [args...]
Ubuntu 24.04 JRE images have pebble enter
as the entrypoint. You can access the java with the following
command:
bash$ docker run --rm ubuntu/jre:21_edge exec java Usage: java [options] <mainclass> [args...] ...
Launch this image locally:
For Ubuntu 22.04 JRE
bashdocker run -d --name jre-container -e TZ=UTC ubuntu/jre:17-22.04_edge
For Ubuntu 24.04 JRE
bashdocker run -d --name jre-container -e TZ=UTC ubuntu/jre:21-24.04_edge exec java
The container logs will simply show the OpenJRE help message. This is because the container expects a compiled Java application to be given.
Let's use the following Hello World application as an example:
java// HelloWorld.java class HelloWorld { public static void main(String args[]) { System.out.println("Hello, World"); } }
You can build and package the above Hello World application with ***led Ubuntu 22.04 JRE 8 and 17 using the following example Dockerfile.
dockerFROM ubuntu:22.04 AS builder RUN apt-get update && apt-get install -y openjdk-8-jdk WORKDIR /app ADD HelloWorld.java . RUN javac -source 8 -target 8 HelloWorld.java -d . FROM ubuntu/jre:8-22.04_edge WORKDIR / COPY --from=builder /app/HelloWorld.class . CMD [ "HelloWorld" ]
For Ubuntu 24.04 please use
dockerFROM ubuntu:24.04 AS builder RUN apt-get update && apt-get install -y openjdk-8-jdk WORKDIR /app ADD HelloWorld.java . RUN javac -source 8 -target 8 HelloWorld.java -d . FROM ubuntu/jre:21-24.04_edge COPY --from=builder /app/HelloWorld.class . CMD [ "exec", "java", "-cp", "/", "HelloWorld" ]
!LTS Up to 5 years of free security maintenance on LTS channels.
!ESM Up to 10 years of customer security maintenance from Canonical's restricted repositories.
| Channel Tags | Supported until | Currently | Architectures | |
|---|---|---|---|---|
21-24.04_stable | 21-24.04, 21-24.04_beta, 21-24.04_candidate, 21-24.04_edge | - | jre 21 on Ubuntu 24.04 LTS | amd64, arm64 |
17-24.04_stable | 17-24.04, 17-24.04_beta, 17-24.04_candidate, 17-24.04_edge | - | jre 17 on Ubuntu 24.04 LTS | amd64, arm64 |
11-24.04_stable | 11-24.04, 11-24.04_beta, 11-24.04_candidate, 11-24.04_edge | - | jre 11 on Ubuntu 24.04 LTS | arm64, amd64 |
8-22.04_edge | 8-22.04_100, 8-22.04_edge_100, 8_edge, edge | - | jre 8 on Ubuntu 22.04 LTS | amd64, arm64 |
17-22.04_edge | 17-22.04_98, 17-22.04_edge_98, 17_edge | - | jre 17 on Ubuntu 22.04 LTS | amd64, arm64 |
track_risk |
Channel Tags shows the most stable channel for that track ordered stable, candidate, beta, edge. More risky channels are always implicitly available. So if beta is listed, you can also pull edge. If candidate is listed, you can pull beta and edge. When stable is listed, all four are available. Images are guaranteed to progress through the sequence edge, beta, candidate before stable.
If your usage includes commercial redistribution, or requires ESM or unavailable channels/versions, please get in touch with the Canonical team (or using ***).
Launch this image locally:
shdocker run -d --name jre-container -e TZ=UTC ubuntu/jre:21-24.04_stable
To debug the container:
shdocker logs -f jre-container
To debug the container:
bashdocker logs -f openjdk-jre-container
For Ubuntu 24.04 JRE, to inspect application logs:
bashdocker exec openjdk-jre-container pebble logs
If you find a bug in our image or want to request a specific feature, please file a bug here:
[***]
Please title the bug "jre: <issue summary>". Make sure to include the digest of the image you are using, from:
shdocker images --no-trunc --quiet ubuntu/jre:<tag>
These channels (tags) are not updated anymore. Please upgrade to newer channels, or reach out if you can't upgrade.
| Track | Version | EOL | Upgrade Path |
|---|---|---|---|
track |

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务