OpenJDK 11 runtime image on UBI9 - Red Hat Ecosystem Catalog

1.21-1.1733995523

latest

1.21

Overview

Description

This is a lean, runtime-only container designed for use as a base for deploying pre-built applications. The container does not contain the Java compiler / JDK tools or Maven. For Builder images, use ubi9/openjdk-11 instead.

Products using this container

Red Hat Universal Base Image 9

Red Hat Universal Base Images (UBI) are OCI-compliant container base operating system images with complementary runtime languages and packages that are freely redistributable.

Containerized application

Red Hat build of OpenJDK

The Red Hat build of OpenJDK is a free and open source implementation of the Java Platform, Standard Edition (Java SE).

Containerized application

Security

Technical information

General information

The following information was extracted from the containerfile and other sources.

Summary	Image for Red Hat OpenShift providing OpenJDK 11 runtime
Description	Platform for running plain Java applications (fat-jar and flat classpath)
Provider	Red Hat
Maintainer	Red Hat OpenJDK <openjdk@redhat.com>

Technical information

The following information was extracted from the containerfile and other sources.

Repository name	ubi9/openjdk-11-runtime
Image version	1.21
Architecture	amd64
Usage	https://rh-openjdk.github.io/redhat-openjdk-containers/
Exposed ports	[\"8080/tcp\" \"8443/tcp\"]
User	185
Working directory	/home/default

Packages

Containerfile

Get this image

Terms & conditionsThe Red Hat Universal Base Image is free to deploy on Red Hat or non-Red Hat platforms and freely redistributable. Software vendors and community projects which build on UBI may have additional EULAs which apply to their layered software. Please refer to the End User License Agreement for the Red Hat Universal Base Image for information about use of the Red Hat Universal Base Image and associated software and source code.

Using registry tokens

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Manifest List DigestCopy to Clipboard

Image DigestCopy to Clipboard

Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.

Using OpenShift secrets

First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.

Copy to Clipboard

Then, use the following from the command line or from the OpenShift Dashboard GUI interface.

Copy to Clipboard

Using podman login

Use the following command(s) from a system with podman installed

Copy to Clipboard

Using docker login

Use the following command(s) from a system with docker service installed and running

Copy to Clipboard

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Manifest List DigestCopy to Clipboard

Image DigestCopy to Clipboard

Use the following instructions to get images from a Red Hat container registry using your Red Hat login.

Using OpenShift

For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.

Using podman login

Use the following command(s) from a system with podman installed

Copy to Clipboard

Using docker login

Use the following command(s) from a system with docker service installed and running

Copy to Clipboard

Unauthenticated

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Manifest List DigestCopy to Clipboard

Image DigestCopy to Clipboard

Update to new container registryTo support our existing users and users to come, we will be transitioning our product portfolio and customers to a new container registry. The new registry uses standard OAuth mechanisms to provide customers with the ability to configure their systems to pull containerized content using static tokens or their Red Hat login. Customers are encouraged to begin using the new registry as their preferred authentication method.

Use the following instructions to get images from a Red Hat container registry without providing authentication.

Using oc

A container image made to run with OpenShift platforms can either be pulled from the command line or from the OpenShift Dashboard GUI interface.

Copy to Clipboard

Using podman

Use the following command(s) from a system with podman installed

Copy to Clipboard

Using docker

Use the following command(s) from a system with docker service installed and running

Copy to Clipboard

Get the source

RegistryCopy to Clipboard

RepositoryCopy to Clipboard

Manifest List DigestCopy to Clipboard

Image DigestCopy to Clipboard

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.
Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Step one

Use skopeo to copy the source image to a local directory

Copy to Clipboard

Step two

Inspect the image

Copy to Clipboard

Step three

Untar the contents

Copy to Clipboard

Step four

Begin examining and using the content.

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.

Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).

The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.

Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

OpenJDK 11 runtime image on UBI9 Deprecated

Description

Products using this container

Red Hat Universal Base Image 9

Red Hat build of OpenJDK

Published

Release category

Size

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Using oc

Using podman

Using docker

Getting source containers

Step one

Step two

Step three

Step four

Platforms

Products & services

Try, buy, sell

Help

About Red Hat Ecosystem Catalog

Red Hat legal and privacy links

Red Hat legal and privacy links

OpenJDK 11 runtime image on UBI9 Deprecated

Description

Products using this container

Red Hat Universal Base Image 9

Red Hat build of OpenJDK

Published

Release category

Size

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Using oc

Using podman

Using docker

Getting source containers

Step one

Step two

Step three

Step four