Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Push fails silently and pushes tags but no images #60

Open
budleigh opened this issue Dec 19, 2021 · 1 comment
Open

[BUG] Push fails silently and pushes tags but no images #60

budleigh opened this issue Dec 19, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@budleigh
Copy link

budleigh commented Dec 19, 2021

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.

@budleigh budleigh added the bug Something isn't working label Dec 19, 2021
@divyansh42
Copy link
Member

@budleigh will it be possible for you to share the complete workflow log?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants