-
Notifications
You must be signed in to change notification settings - Fork 41
Description
Problem description
When I build and push OCI images using the buildah
CLI to dockerhub, they get pushed fine (and can be pulled with buildah pull ...
), but they won't show up in the Dockerhub UI, nor can they be pulled by the docker
CLI or Kubernetes (using Docker). But Docker does appear to see that the image exists
docker pull:
johns-mbp-3:~ johncollier$ docker pull johncollier/spring-push-test
Using default tag: latest
Error response from daemon: mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not ''
buildah pull
sh-4.2# buildah pull johncollier/spring-push-test
Getting image source signatures
Copying blob edf72af6d627 skipped: already exists
Copying blob 8d3eac894db4 skipped: already exists
Copying blob 3e4f86211d23 skipped: already exists
Copying blob d72258b97fd0 skipped: already exists
Copying blob efaa572fa153 skipped: already exists
Copying blob f7277927d38a skipped: already exists
Copying blob 4b9886dd7157 skipped: already exists
Copying blob f81d814c0c2c skipped: already exists
Copying blob 3dcc376f5183 skipped: already exists
Copying config 7765f9ec00 done
Writing manifest to image destination
Storing signatures
7765f9ec00b0adc6cc1469535241b886deaf0b69e16617837d7608627bf6f3da
This seems to be a recent change, as up until yesterday, using the exact same version of buildah
, everything worked fine and OCI images could be pushed to DockerHub using buildan and they could be pulled using Kubernetes/Docker (and seen in the DockerHub UI).
I should also note that other Docker registries work perfectly fine without issue (such as Artifactory, OKD's internal registry, etc). I can push images to them using buildah
and Kubernetes can pull them perfectly fine.