Open demensdeum opened 6 months ago
Reproducable only on Arch Linux and MacOS M2. Everything good on Windows 11.
š @demensdeum -- any chance you've given this a try lately? I was able to build on and M1 running MacOS 14.2.1 and github.com/docker/buildx v0.14.0-desktop.1
.
@thompson-shaun I will try and respond
I have the same issue when trying to update to buildkit v0.12.5 (and docker:27.1.1) from docker 19. After reading the initial post here I also tried it with docker:25.0.5 and docker:24.0.9 and the outcome is exactly the same.
on amd64
default docker
\_ default \_ default running v0.12.5 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386
on arm64
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
default* docker
\_ default \_ default running v0.12.5 linux/arm64, linux/arm/v7, linux/arm/v6
After trying to update the docker-engine (and switching to buildx) for a large docker image build (based on Ubuntu 20.04.6 LTS).
ERROR: failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF
It consistently fails (30 out of 30 tries) after completing roughly half the build which is at 100 minutes in.
I have tried disabling inline cache with BUILDKIT_INLINE_CACHE=0
as suggested in some tickets
š @lenhartd-apex - What version did you update to that produced the failed to receive status
terminal output above?
@thompson-shaun
š @lenhartd-apex - What version did you update to that produced the
failed to receive status
terminal output above?
I updated to buildkit v0.12.5 (and docker:27.1.1)
? Maybe I phrased this ambiguously: "After trying to update the docker-engine". What I meant is: I tried to update to buildkit v0.12.5 (and docker:27.1.1)
and face this issue. I tried to update to an older version (25 and 24) and they all have the same issue. Only going back to 19 fixes it.
Contributing guidelines
I've found a bug and checked that ...
Description
git clone https://github.com/demensdeum/Masonry-AR-Docker.git cd Masonry-AR-Docker docker buildx build .