Closed mreiche closed 12 months ago
We tried to debug registry-image
by adding
debug: true
since then, the bug is gone for 24h now.
We switch back to docker-image
.
@mreiche I'm late to the party, but I happened across your issue. I am wondering if its related to this current issue https://github.com/concourse/registry-image-resource/issues/356 I just filed where using images built with newer versions of docker fail to push using registry-image concourse resource. The details looks fairly similar.
It's probably too late for you to dig into the details or reproduce, but thought I'd mention it.
Describe the bug
I have some
registry-image
resources, pulling from private Artifactory.build-meta-data
bitbucket-pull-request
Both are failing, because of the following reasons:
Both resources pulling
1f8c0fd22ad21032f9464a86c51d97c0228bdd8be44fd10616ea16e331220a4b
, no matter which tag or SHA was given.I took a look into Artifactory's access log:
I checked the
manifest.json
for the SHA, because I was thinking that Artifactory has a bug resolving tags. But then I found more logs like that in the request log, that shows that Artifactory get requested for the same resource hash for several other images:Where does
1f8c0fd22ad21032f9464a86c51d97c0228bdd8be44fd10616ea16e331220a4b
comes from? I do not find any image with this SHA in the Artifactory nor do i find it in theresource_caches
table of Concourse:Is there a bug somewhere between
image-registry
and orgo-containerregistry
?I also tried to get rid of caches by deleting Worker PVCs and re-creating the Pipeline completely.
Reproduction steps
I dont know if there are steps to reproduce.
Expected behavior
image-registry
should pull the right image.Additional context
No response