[v0.23] ERROR: failed to read expected number of bytes: unexpected EOF #6036
Description
Contributing guidelines and issue reporting guide
- I've read the contributing guidelines and wholeheartedly agree. I've also read the issue reporting guide.
Well-formed report checklist
- I have found a bug that the documentation does not mention anything about my problem
- I have found a bug that there are no open or closed issues that are related to my problem
- I have provided version/information about my environment and done my best to provide a reproducer
Description of bug
Bug description
I tried to upgrade to yesterday's release v0.23.0 and have a consistant error.
ERROR: failed to read expected number of bytes: unexpected EOF
There is no error on v0.22.0
#8 [grpc_reverse_proxy context envoy] load metadata for envoyproxy/envoy:v1.34-latest
#8 ERROR: failed to read expected number of bytes: unexpected EOF
#7 [nxdh-base] resolve image config for docker-image://docker.io/docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d
#7 ERROR: failed to read expected number of bytes: unexpected EOF
------
> [nxdh-base] resolve image config for docker-image://docker.io/docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d:
------
------
> [grpc_reverse_proxy context envoy] load metadata for envoyproxy/envoy:v1.34-latest:
------
Dockerfile:1
--------------------
1 | >>> FROM envoy
2 |
3 | SHELL ["/bin/bash", "-Eeuo", "pipefail", "-c"]
--------------------
ERROR: target grpc_reverse_proxy: failed to solve: failed to resolve source metadata for docker.io/envoyproxy/envoy:v1.34-latest: failed to read expected number of bytes: unexpected EOF
Command execution failed.#7 [reverse_proxy] resolve image config for docker-image://docker.io/docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d
#7 ERROR: failed to read expected number of bytes: unexpected EOF
#8 [grpc_reverse_proxy context envoy] load metadata for envoyproxy/envoy:v1.34-latest
#8 ERROR: failed to read expected number of bytes: unexpected EOF
------
> [grpc_reverse_proxy context envoy] load metadata for envoyproxy/envoy:v1.34-latest:
------
------
> [nxdh-base] resolve image config for docker-image://docker.io/docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d:
------
Dockerfile:1
--------------------
1 | >>> # syntax=docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d
2 |
3 | FROM base
--------------------
ERROR: target reverse_proxy: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1@sha256:9857836c9ee4268391bb5b09f9f157f3c91bb15821bb77969642813b0d00518d: failed to read expected number of bytes: unexpected EOF
Command execution failed.
Reproduction
Sorry I can't give a reproduction right now. I have a large bake file with cache-to/cache-from opts set.
We also override dockerhub with an internal mirror (artifactory), but this shouldn't cause any issues.
# Override dockerhub registry
[registry."docker.io"]
mirrors = ["dockerhub-mirror.example.com"]
[registry."dockerhub-mirror.example.com"]
# opts for this entry
Version information
buildx: github.com/docker/buildx v0.21.2 1360a9e8d25a2c3d03c2776d53ae62e6ff0a843d
docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
multi-arch-builder* docker-container
\_ multi-arch-builder0 \_ unix:///var/run/docker.sock running v0.23.0 linux/amd64 (+3), linux/386