Experiencing unknown blob error on push about build-push-action

[gudleik]

I tried building and pushing without using this package, and experienced same errors.
When I changed from using short prefixed sha (sha-abcdefg) to full sha as image tags, the problem disappeared.

Maybe you can make tagging a little more customizable, like

# use full sha
uses: docker/build-push-action@v1
with:
  tag: ${{GITHUB_SHA}}

# prefixed short sha like today
uses: docker/build-push-action@v1
with:
  tag: sha-${{GITHUB_SHA::7}}

[crazy-max]

@bhordupur #148 (comment)

[prise6]

Any news on this ?
Got same issue. I wonder if this linked to limited free space for public projet ?

[leoschweizer]

Seeing this error as well all of a sudden - but I'm not using sha tags at all, it is just the latest tag which it has always been 🤔

[derTobsch]

@leoschweizer same here. We also use the latest tag see https://github.com/synyx/urlaubsverwaltung/runs/679001614#step:6:26

[RichiCoder1]

ditto. Seeing this pretty consistently.

[wujood]

I have the same issue, but it seems that if you retry it a couple of times it sometimes works. This seems to be a general issue?

[crazy-max]

Version 2 has been merged to the main branch and is therefore available via uses: docker/build-push-action@v2 (mutable tag).

As a reminder, this new version changes drastically and works with 3 new actions (login, setup-buildx and setup-qemu) that we have created. Many usage examples have been added to handle most use cases.

Can you try with it? Btw I don't think this is related to this action but an issue with the GitHub Package Registry itself. You can get support about GitHub Packages here. Thanks.

[bhordupur]

I have the same issue, but it seems that if you retry it a couple of times it sometimes works. This seems to be a general issue?

We have got the same issue last from yesterday as well. After trying 2/3 times it works. And sometimes even on the first try, it works.

[bhordupur]

Some time ago, we have got this fixed. It was the issue from the Azure side though.

[lupusllc]

@bhordupur we've been having this happen intermittently for quite some time to Azure Container Registries, what was the issue they/you found on the Azure side?

[bhordupur]

We have had geo-replication enabled for the ACR registry. We needed to disable the routing to the edge location which seemed to fix the issue. After a week if I remember correctly we enabled it. The issue is also documented on the Azure side. Here is the link.

Before that, we tried to delete the tag from the remote ACR and pushed the same image and it was more of luck. In some pushes, it worked without issues and others did not. @lupusllc