Skip to content

[OPENJDK-3686] update jlink README with RHEC link, customer focus #575

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: jlink-dev
Choose a base branch
from
Open

[OPENJDK-3686] update jlink README with RHEC link, customer focus #575

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 15 additions & 4 deletions templates/jlink/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,12 @@ DISCLAIMER: This template requires OpenShift to be able to resolve ImageStreams,

## Stage 0: UBI9 OpenJDK ImageStreams with jlink-dev changes

Until the `jlink-dev` work is merged, prior to trying out the template, we must first
prepare UBI9 OpenJDK ImageStreams with `jlink-dev` support.
Whilst the `jlink-dev` feature is in Tech Preview, we must prepare separate
UBI9 OpenJDK ImageStreams with `jlink-dev` support.

1. Build a suitable OpenJDK container image from [this
repository](https://github.com/jboss-container-images/openjdk),
1. Obtain a suitable OpenJDK container image with Jlink integration.
Either download [the Tech Preview Image](https://catalog.redhat.com/software/containers/openjdk-tech-preview/openjdk-21-jlink-rhel9/678e61ffd77a3837d6962f3f?),
or build your own from [this repository](https://github.com/jboss-container-images/openjdk),
branch `jlink-dev`. e.g.

cekit --descriptor ubi9-openjdk-21.yaml build podman
Expand All @@ -36,10 +37,20 @@ prepare UBI9 OpenJDK ImageStreams with `jlink-dev` support.
"insecure-registries": [ "default-route-openshift-image-registry.apps-crc.testing" ]
}

For podman, add the following to `~/.config/containers/registries.conf`:

[[registry]]
location = "default-route-openshift-image-registry.apps-crc.testing"
insecure = true

5. Log into the OpenShift registry, e.g.

REGISTRY_AUTH_PREFERENCE=docker oc registry login

or

oc registry login

6. tag and push the dev image into it. The OpenShift console gives you the
exact URI for your instance

Expand Down