You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the get step, we get the following error message:
fetching rabbitmq@sha256:7c592e6c6b3510fa4353fa078ee3d5bd0b0ea5500ddee31607b964f02d0b46e2
ERRO[0000] failed to write OCI image: unsupported status code 404; body: 404 page not found
However, we are able to docker pull this image. Worth mentioning, this image has another SHA rabbitmq@sha256:76346c31d3eee20f82ebc2573cb0be891e4827b35e875f53cc93c9df76143732 that is docker pullable and it works fine with the registry image resource.
The text was updated successfully, but these errors were encountered:
I'm seeing this issue as well for the following images:
fetching eclipse-mosquitto@sha256:d6d255052b779cdc704418710d30638bf387e6d8e4e707feb6a7a580e184b748
ERRO[0000] failed to write OCI image: unsupported status code 404; body: 404 page not found
fetching postgres@sha256:e874e4ecbc8f9846027a4132f32a41700e70ac6e0f804ad26fec5b3ab2cd6cff
ERRO[0000] failed to write OCI image: unsupported status code 404; body: 404 page not found
fetching zookeeper@sha256:4879178a575d76d5720602f81107be4d165107ab03de0b26669605a5d39d656d
ERRO[0000] failed to write OCI image: unsupported status code 404; body: 404 page not found
We found an issue with registry image where an image available in Docker Hub and
docker pull
able failed in theget
step of a job.The image failing in the
get
step is from RabbitMQ Docker Hub:This is how our resource definition and job is configured:
In the
get
step, we get the following error message:However, we are able to
docker pull
this image. Worth mentioning, this image has another SHArabbitmq@sha256:76346c31d3eee20f82ebc2573cb0be891e4827b35e875f53cc93c9df76143732
that isdocker pull
able and it works fine with the registry image resource.The text was updated successfully, but these errors were encountered: