Experiencing unknown blob error on push
See original GitHub issueI have a workflow containing multiple jobs building and pushing images to Github Packages.
This works great most of the time, but sometimes a random job is failing during docker push with an unknown blob
error.
The jobs are declared like this:
build-maintenance:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: docker/build-push-action@v1
with:
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
registry: docker.pkg.github.com
repository: XXX/YYY/maintenance
path: maintenance
target: production
tag_with_sha: true
Tail of job output:
Successfully built c6ac9d5faeba
Successfully tagged docker.pkg.github.com/XXX/YYY/maintenance:sha-eac817d
Pushing image [docker.pkg.github.com/XXX/YYY/maintenance:sha-eac817d]
The push refers to repository [docker.pkg.github.com/XXX/YYY/maintenance]
1e64616ff473: Preparing
02e9da9d44c5: Preparing
3810cc0c140f: Preparing
3e207b409db3: Preparing
3e207b409db3: Layer already exists
3810cc0c140f: Layer already exists
unknown blob
Error: exit status 1
exit status 1
Usage:
github-actions build-push [flags]
Flags:
-h, --help help for build-push
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:12 (2 by maintainers)
Top Results From Across the Web
unknown blob on docker push to gcp - Stack Overflow
I have a CI/CD build system running on GCP cloud build. It sporadically fails upon dock push with error: "unknown blob" (see below)....
Read more >How to resolve the “Unknown blob” error when pulling ... - JFrog
We have seen several cases when customers trying to perform 'docker pull' and facing the ”unknown blob” error due to URLs that need...
Read more >BLOB Upload Unknown error while pushing Docker Image to ...
Hi,. I am setting up cicd in github action to digital ocean kuberntes and using digital ocean container registry for my images.
Read more >pushing manifest to registry gets error "manifest blob unknown"
Because the individual manifests were pushed to the child repository, their blobs won't be in the parent repository, and thus the manifest blob...
Read more >HTTP API V2 - Docker Documentation
This error may be returned when a manifest blob is unknown to the registry. MANIFEST_INVALID, manifest invalid, During upload, manifests undergo several checks ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
@bhordupur https://github.com/docker/build-push-action/issues/148#issuecomment-702278002