Skip to content

Commit

Permalink
Describe configuring Docker to avoid TLS verifying OCP registry
Browse files Browse the repository at this point in the history
Thanks Jaya for the suggestion.

Signed-off-by: Jonathan Dowland <[email protected]>
  • Loading branch information
jmtd committed Apr 16, 2024
1 parent 60b9820 commit 60cffc2
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions templates/jlink/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,19 @@ prepare UBI9 OpenJDK ImageStreams with `jlink-dev` support.

oc create imagestream ubi9-openjdk-17

3. Log into the OpenShift registry, e.g.
3. You may need to configure your container engine to not TLS-verify the OpenShift
registry. For Docker, add the following to `/etc/docker/daemon.json` and restart
the daemon:

{
"insecure-registries": [ "default-route-openshift-image-registry.apps-crc.testing" ]
}

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

REGISTRY_AUTH_PREFERENCE=docker oc registry login

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

docker tag ubi9/openjdk-17:1.18 default-route-openshift-image-registry.apps-crc.testing/jlink1/ubi9-openjdk-17:1.18
Expand Down

0 comments on commit 60cffc2

Please sign in to comment.