Images not shown in pull through cached ECR repository

0

Hello,

I have set up the pull through cache, using the new repository template feature, with cross account access. I can pull upstream images just fine, the repository is automatically created with the templates settings:

$ podman pull 1234567.dkr.ecr.eu-central-1.amazonaws.com/quay/keycloak/keycloak:23.0
Trying to pull 1234567.dkr.ecr.eu-central-1.amazonaws.com/quay/keycloak/keycloak:23.0...
Getting image source signatures
Copying blob 7e11c5ba1fd2 skipped: already exists  
Copying blob a4503341e3e7 skipped: already exists  
Copying blob 65b190d0545b skipped: already exists  
Copying blob f72461870632 skipped: already exists  
Copying config 33825b7d2d done   | 
Writing manifest to image destination
33825b7d2d9e317215939851e10b1e184b4f876de1b5b25cf448e425c47802bd

However, when I look into the UI, or try and list the images in the ECR, nothing is shown, even though I literally just successfully pulled the image from this very repository:

$ aws ecr list-images --repository-name quay/keycloak/keycloak 
{
    "imageIds": []
}

The UI says no images to display: ECR repo with no image

Any help is highly appreciated. I tried changing from KMS to AES-256, with and without repo lifecycle, all to no avail. The functionality is given from a user perspective, the pull works, but I'd expect the layers to be visible in the repository. According to this video https://youtu.be/uTyrld7jVrk?t=1703 I should be able to see the cached layers just like if I pushed them, but they're not there.

What am I missing, please?

gefragt vor 4 Monaten158 Aufrufe
1 Antwort
0
Akzeptierte Antwort

Started working after a while :shrug:.

beantwortet vor 3 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen