abiosoft / abiosoft/colima

Error when building and pushing images: "blob upload invalid: None of the provided layer digests match the calculated layer digest"

Open
#1,167 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
30.8k
Forks
613
PR merge metrics
No merged PRs in 30d

Description

### Description

I'm experiencing an issue when trying to build an image with the `DOCKER_BUILDKIT=1 docker build` command and push it to AWS ECR. The error message I receive is:

```
blob upload invalid: None of the provided layer digests match the calculated layer digest
```
It seems that the calculated layer is missing a portion of its data. For example, the output shows:

```
ccba602a: Pushing 204.1MB/443.4MB
ccba602a: Pushing 523.3MB
```
After this, we experience about 5 retries, and then the error above appears.

Could you please investigate this issue? Any insights or recommendations for resolving it would be greatly appreciated.

### Version

colima version 0.7.5
git commit: 1588c066b9ab9dae8205ef265929c7eb43dca473

runtime: docker
arch: aarch64
client: v27.1.1
server: v27.1.1
limactl version 0.23.2
qemu-img version 9.1.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [x] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/my_user/.colima/default/docker.sock

### Reproduction Steps

1. Build the image with the `DOCKER_BUILDKIT=1 docker build`.
2. Tag the image with the `docker tag` command
3. Using the `docker push` command

### Expected behaviour

Image pushed to AWS ECR.

### Additional context

I've also pruned Docker (`docker system prune`) and deleted Colima (`colima delete`). I've tried using everything fresh, but the same issue still appears.

I’ve noted that some users with earlier versions of Colima are able to build and push the same project without encountering this issue. This leads me to believe there may have been a change in the release that could be causing the problem. Their version:

colima version HEAD-a58166e
git commit: a58166e288acc54cc98d890fad49a643203b04e8

runtime: docker
arch: aarch64
client: v27.3.1
server: v24.0.9
limactl version 0.23.2
qemu-img version 9.1.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.