Description of problem: oc new-app --search nodejs throws a warning that "you may not have access to the container image "docker.io/library/nodejs:latest" Why are we still going to docker.io for sample content? Shouldn't this be quay.io or registry.redhat.io? oc new-app --search ruby does not throw the warning. # oc new-app --search nodejs W0202 20:37:38.073924 2400977 dockerimagelookup.go:300] container image remote registry lookup failed: you may not have access to the container image "docker.io/library/nodejs:latest" Templates (oc new-app --template=<template>) ----- nodejs-postgresql-example Project: openshift An example Node.js application with a PostgreSQL database. For more information about using this template, including OpenShift considerations, see https://github.com/nodeshift-starters/nodejs-rest-http-crud/blob/master/README.md. WARNING: Any data stored will be lost upon pod destruction. Only use this template for testing. nodejs-postgresql-persistent Project: openshift An example Node.js application with a PostgreSQL database. For more information about using this template, including OpenShift considerations, see https://github.com/nodeshift-starters/nodejs-rest-http-crud/blob/master/README.md. Image streams (oc new-app --image-stream=<image-stream> [--code=<source>]) ----- nodejs Project: openshift Tags: 14-ubi8, 14-ubi8-minimal, 16-ubi8, 16-ubi8-minimal, latest jenkins-agent-nodejs Project: openshift Version-Release number of selected component (if applicable): 4.10.0-rc.0 How reproducible: always Steps to Reproduce: 1. oc new-app --search nodejs 2. 3.
Hum, checking on this, I would also expect it to be quay.io or registry.redhat.io
I do see a few image streams that still use docker.io but nodejs is not one of them: https://github.com/openshift/cluster-samples-operator/search?q=docker.io Could this be a tag that was added after Samples was installed?
This is a build thing, not samples, and I believe is related to https://github.com/openshift/oc/pull/742 and https://bugzilla.redhat.com/show_bug.cgi?id=1928850 which I handled last year It is EOB here but I'll refresh my memory with this PR/BZ ^^ tomorrow and see if we either missed something there, or if there is some working as designed elements, were we still have to check docker.io based on how the docker client works, even if we ultimately also check quay.io, registry.redhat.io, etc.
Verified with 4.11 image ================== $ oc new-app --search nodejs Templates (oc new-app --template=<template>) ----- nodejs-postgresql-example Project: openshift An example Node.js application with a PostgreSQL database. For more information about using this template, including OpenShift considerations, see https://github.com/nodeshift-starters/nodejs-rest-http-crud/blob/master/README.md. WARNING: Any data stored will be lost upon pod destruction. Only use this template for testing. nodejs-postgresql-persistent Project: openshift An example Node.js application with a PostgreSQL database. For more information about using this template, including OpenShift considerations, see https://github.com/nodeshift-starters/nodejs-rest-http-crud/blob/master/README.md. Image streams (oc new-app --image-stream=<image-stream> [--code=<source>]) ----- nodejs Project: openshift Tags: 14-ubi8, 14-ubi8-minimal, 16-ubi8, 16-ubi8-minimal, latest jenkins-agent-nodejs Project: openshift Tags: latest, v4.0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069