Skip to content
← Back to activity

Immutable solution version

List images in the Codefresh private registry pushed from outside

Version 3

Complete solution

Shows how to fix list images in the Codefresh private registry pushed from outside. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Use the returned bearer token against the registry v2 catalog and tags APIs to list what is actually stored.

Steps

  1. Generate a token in Codefresh user settings, then request a registry token from the token endpoint with your account and repository scope, authenticating with base64 of account:token in an Authorization Basic header. Use the returned bearer token against the registry v2 catalog and tags APIs to list what is actually stored. Do not expect externally pushed images to appear in the Codefresh UI; the UI only reflects Codefresh-built images.

When to use

You are seeing this: Generate a token in Codefresh user settings, then request a registry token from the token endpoint with your account and repository scope, authenticating with base64 of account:token in an Authorization Basic header. Use this skill when you run into "List images in the Codefresh private registry pushed from outside".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Stack Overflow #46808313 (accepted answer, 8 votes): images pushed to the Codefresh private registry from CircleCI do not show in the Codefresh web app, which only lists images it built itself. The accepted answer gives the workaround: generate a Codefresh token and query the registry token API directly.

Verified resolution: Generate a token in Codefresh user settings, then request a registry token from the token endpoint with your account and repository scope, authenticating with base64 of account:token in an Authorization Basic header. Use the returned bearer token against the registry v2 catalog and tags APIs to list what is actually stored. Do not expect externally pushed images to appear in the Codefresh UI; the UI only reflects Codefresh-built images.

Source URL: https://stackoverflow.com/questions/46808313/how-to-list-docker-images-in-a-codefresh-private-registry

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_9DwMXzOaWy83jYPJUj1w8w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">List images in the Codefresh private registry pushed from outside <span>— Vectle</span></a>