Skip to content
Open
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion build/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.5 AS builder
FROM quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.6 AS builder
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Verify the current digest behind the tag on Quay (read-only)
TOKEN="$(curl -fsSL 'https://quay.io/v2/auth?service=quay.io&scope=repository:redhat-services-prod/openshift/boilerplate:pull' | jq -r '.token')"

curl -fsSI \
  -H "Authorization: Bearer ${TOKEN}" \
  -H 'Accept: application/vnd.docker.distribution.manifest.v2+json' \
  'https://quay.io/v2/redhat-services-prod/openshift/boilerplate/manifests/image-v8.3.6' \
  | tr -d '\r' | awk -F': ' '/Docker-Content-Digest/ {print $2}'

Repository: openshift/managed-node-metadata-operator

Length of output: 66


🌐 Web query:

quay.io redhat-services-prod openshift boilerplate image-v8.3.6 docker

💡 Result:

I couldn’t verify the exact image reference you provided: quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.6. What I could verify from authoritative sources is: - The upstream OpenShift boilerplate repository uses image tags named image-v{X}.{Y}.{Z} and documents that those tags correspond to build images produced from Konflux/CI [1]. - In the boilerplate repository, the latest release I found is image-v8.3.4 (published 2026-02-25) [2]. I did not find any public evidence (in the searched sources) that an image-v8.3.6 release exists as of today (2026-05-11). So, with high confidence based on the sources above: - Image-v8.3.6 is not confirmed publicly in the boilerplate release tags I found; the most recent confirmed boilerplate build image tag is image-v8.3.4 [2]. If you want, share the full intended docker image name format you’re using (including whether “openshift/boilerplate” is actually the repository path on Quay or whether there’s an additional component like openhshift-user-workloads, user-workloads, or a tenant namespace). Then I can re-check for the exact v8.3.6 tag under the correct Quay path.

Citations:


🏁 Script executed:

# Check if the image exists and what the previous tag was
cd build && cat -n Dockerfile | head -20

Repository: openshift/managed-node-metadata-operator

Length of output: 918


🏁 Script executed:

# Try alternative approach to verify the image is valid
# Check if we can find any references to this image in the codebase
rg "quay.io/redhat-services-prod/openshift/boilerplate" --type dockerfile --type yaml --type json

Repository: openshift/managed-node-metadata-operator

Length of output: 119


🏁 Script executed:

# Search for references to the image across the repo
rg "image-v8.3.6" --type yaml --type json --type text

Repository: openshift/managed-node-metadata-operator

Length of output: 113


🏁 Script executed:

# Check if there's any changelog, release notes, or documentation about v8.3.6
fd -e md -e txt | xargs grep -l "8.3.6" 2>/dev/null | head -10

Repository: openshift/managed-node-metadata-operator

Length of output: 66


Verify the base image tag image-v8.3.6 exists.

The tag image-v8.3.6 does not appear in the publicly available boilerplate releases—the latest confirmed release is image-v8.3.4 (published 2026-02-25). Builds with this tag will fail with an image-not-found error. Either use a confirmed existing tag or clarify if this version is scheduled for release and available in your registry.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@build/Dockerfile` at line 1, The Dockerfile's FROM line references a
non-existent base image tag image-v8.3.6 which will cause image-not-found
failures; update the FROM instruction to use a confirmed existing tag (for
example image-v8.3.4) or replace it with the correct registry/tag your CI uses,
and if image-v8.3.6 is intentional, confirm and document its availability in the
registry so the FROM line in the Dockerfile reflects an actual, accessible tag.


WORKDIR /workspace
# Copy the Go Modules manifests
Expand Down