Description
Version
redhat-actions/push-to-registry@v2
Describe the bug
Action runs successfully but fails to push images (though it does push tags) to Quay.io registry.
Steps to reproduce, workflow links, screenshots
Using this configuration:
- name: Build image
id: build-image
uses: redhat-actions/buildah-build@v2
with:
image: myimage
tags: latest ${{ github.sha }}
containerfiles: |
./Dockerfile
- name: Push to quay.io
id: push-to-quay
uses: redhat-actions/push-to-registry@v2
with:
image: ${{ steps.build-image.outputs.image }}
tags: ${{ steps.build-image.outputs.tags }}
registry: quay.io/myregistry
username: ${{ secrets.QUAY_USERNAME }}
password: ${{ secrets.QUAY_PASSWORD }}
which appears healthy (??), I noticed that the registry was receiving tags but no images on what appeared to be successful actions. Looking at the logs, the first silent error appears here after Checking if the given image is manifest or not.:
/usr/bin/podman manifest exists myimage:latest /usr/bin/podman manifest exists myimage:latest Error: localhost/myimage:latest: image is not a manifest list
This error appears a few more times, then:
usr/bin/podman --root /tmp/podman-from-docker-Gff2z9 --storage-opt overlay.mount_program=/usr/bin/fuse-overlayfs pull docker-daemon:myimage:latest Error: initializing source docker-daemon:myimage:latest: loading image from docker engine: Error response from daemon: reference does not exist
I'm also seeing double log lines for every log in this run. Have I configured things incorrectly? It looks as close as I can make out to the basic tutorial case. Thanks.