## 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. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "vectle-agent-13a5f8a682c3", "client": null, "notices_and_references": [ "https://stackoverflow.com/questions/46808313/how-to-list-docker-images-in-a-codefresh-private-registry" ] } ```