http2: server: error reading preface from client //./pipe/docker_engine: file has already been closed #13611
Comments
|
I got this message for just some "docker build", not every "docker build". This message is shown in startup operation of docker build command. Note: I have no "ddev" executable/script in my disk. |
|
I am encountering the same issue where the updated changes are not reflected in the built image, and the system continues to run using the older image. |
|
Facing the same issue on latest version (4.26.0), solution is to revert back to an older version (e.g.: https://docs.docker.com/desktop/release-notes/#4251) for the moment being. |
|
I've hit the same issue when I updated to latest wsl version ( $ wsl --version
WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3693.wslconfig Steps to reproduce
I build docker images which inherit/depend from each other. Example: Image C from Image B from Image A. Actual behaviorImages are build successfully with the mentioned error before img B and img C builds. Example with pseudo-code: Expected behaviorImages are build successfully with no error printed out. LogsI've collected the following logs:
|
|
Hey, we hit this one as well, what's the status here? Do we know if this is error or just a warning, does docker build / push finishes as expected with this message or result should be discarded and the action repeated? |
|
I have the same issue with the last Docker and a pre-released WSL: This also probably fills random files with zeros after some position. In my case there two files were erased after the 48 MB offset (300_0000h), but the file sizes have not changed. @bjg2 I think you need to repeat the builds with such error. Maybe related docker/compose#11165 |
|
same issue.And my dockerfile's change dose not work. Restart did not work too. It's confused.... |
|
Faced same again with 4.27.1 (136059) |
|
Hi there, I have the same error, the moment I upgraded Docker Desktop for Windows to 4.27.1 I got the error. This is the error: It comes from this Dockerfile: #specify the base image with your desired version curity/idsvr: RUN rm -rf /opt/idsvr/etc/init/* COPY opt/ /opt/ #Copy the overriden template folders for the UI-Builder to change our look and feel of the Curity UI USER root #Enable local debugging tools RUN chmod -R 755 /opt/idsvr/usr/bin/post-commit-scripts/ USER idsvr:idsvr PLEASE NOTE:If I comment OUT these lines, the Dockerfile will work: I've downgraded to version 4.26.1 and now everything works again. I even tried to run "docker builder prune -af" to clear all cache ( it cleared out 40GB of cache on my machine ) when I was running 4.27 and restarted it multiple times to try to fix it but nothing worked. Version 4.27 is broken. Please fix it |
|
For me downgrading to v.26.1 (from 27.1) helped. |
as you can see above, that was also my "fix". To downgrade to 26.1 But 27.1 needs to be fixed properly Is anybody from Docker monitoring this issue? Can you confirm that this is being worked on? |
|
can you test with the latest 4.27.2? https://docs.docker.com/desktop/release-notes/#4272 |
|
For me it still appears in version 4.27.2 I have following windows version OS Name Microsoft Windows 10 Enterprise |
Likewise for me too |
Nice! It works with 4.27.2 which you just released, just confirmed it ;-) Thanks! |
Still happening in latest version |
This is a long shot, but could it be a Windows version specific? For me it's happening on Windows 10 but not Windows 11? |
In my case (Windows 10 21H2 19044.3930) didn't helped. But downgrading to 4.26.1 didn't helped as well. |
|
I had the issue on 4.27.1 and confirmed 4.27.2 fixed the issue |
Is still happening in 4.27.2, a system reboot did not help. Layers are not getting persisted during builds. OS Name Microsoft Windows 10 Enterprise |
|
i faced it today on windows 11 with v4.27.2. |
|
I also faced it today on version v4.27.1, updating to v4.27.2 fixed it |
|
4.27.1 is broken, 4.27.2 is not, but it still logs the error mentioned in the first post. |
|
I have also found that it works correctly through WSL |
|
its still happening in win 10 with v4.27.2 |
|
Came here looking for a solution after updating docker to 4.27.2 on Win 11 |
|
its still happening in win 10 with v4.27.2 |
|
Happened for me aswell on Windows 11 before a popup asking me if we should allow Docker to use my network. After i approved that it no longer shows the message |
|
Getting the same error as well in docker compose
|
|
Same problem met on Win11 with v4.27.2. |
|
Is this issue getting fixed? I'm getting this issue very often, it affects my productivity... |
|
Same problem on Win11 with v4.28.0 |
|
Same here on windows 11 with 4.28.0 |
|
same here windows 10 with 4.28.0 |
|
I went back to 4.26.0 and the error persists. I think I'm stuck since I installed the upgrades. |
|
Not sure if this helps, I initially didn't get this error if I ran |
|
for me once I updated to ddev 1.22.7 everything works. |
|
I rolled back to 4.20.1 and the issue no longer occurs. I am not sure which specific release results in the issue appearing. |
|
Hitting this issue with |
|
4.28.0 fixed it partially. I had some containers that would build prior to 4.28.0 and some that wouldn't. With 4.27.2 I couldn't even re-build some containers that previously worked if I'd roll back, and 4.28.0 fixed THAT issue, but containers that hadn't worked in a few months even when rolling back still are not working with 4.28.0 for me. |
|
I am experiencing this issue in 4.28.0 on Windows 10 as well. Just before (or after?) updating docker, I moved my docker-desktop-data image file onto a separate hard drive in my PC using the docker desktop app's settings to change the storage location. |
|
I encountered the same issue, but it was resolved when I used the --no-cache option with the docker build command. I suspect the problem is related to caching; despite making changes to my code, the hash value of the layer didn’t change after the COPY command. This caused Docker to use an outdated cache, leading to an incorrect image build. |
|
I see the same error. The clearing of cache was NOT helpful for me. Only coincidence? I have often to reset the docker after starting to use vite.-server. |
|
Also cause problems on Docker Desktop 4.25.1. F:\Users\Sergey\Projects\PyProjects\TEst> docker-compose -f compose.yaml -p test up --force-recreate -d --build
2024/04/26 00:05:08 http2: server: error reading preface from client //./pipe/docker_engine: file has already been closed
[+] Building 0.5s (6/6) FINISHED docker:default
=> [app2 internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 407B
... (build success)F:\Users\Sergey\Projects\PyProjects\TEst> wsl --version
Версия WSL: 2.1.5.0
Версия ядра: 5.15.146.1-2
Версия WSLg: 1.0.60
Версия MSRDC: 1.2.5105
Версия Direct3D: 1.611.1-81528511
Версия DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Версия Windows: 10.0.19045.4291
F:\Users\Sergey\Projects\PyProjects\TEst> docker --version
Docker version 24.0.6, build ed223bc
F:\Users\Sergey\Projects\PyProjects\TEst> docker version
Client:
Cloud integration: v1.0.35+desktop.5
Version: 24.0.6
API version: 1.43
Go version: go1.20.7
Git commit: ed223bc
Built: Mon Sep 4 12:32:48 2023
OS/Arch: windows/amd64
Context: default
Server: Docker Desktop 4.25.1 (128006)
Engine:
Version: 24.0.6
API version: 1.43 (minimum version 1.12)
Go version: go1.20.7
Git commit: 1a79695
Built: Mon Sep 4 12:32:16 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.22
GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version: 1.1.8
GitCommit: v1.1.8-0-g82f18fe
docker-init:
Version: 0.19.0
GitCommit: de40ad0
F:\Users\Sergey\Projects\PyProjects\TEst> |
|
i have the same issue with Docker Desktop 4.29.0 on Windows 10 22H2 when running
Client:
Version: 26.0.0
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.13.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.26.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.27
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.23
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.1.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.6.3
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 2
Running: 2
Paused: 0
Stopped: 0
Images: 4
Server Version: 26.0.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.146.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.27GiB
Name: docker-desktop
ID: e0e4e260-8e89-4b64-a2d4-9d4b816739e7
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\\.\pipe\docker_cli
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.4291 |
|
Okay, I give up, I spent way too many hours and days on this issue. I tried many different versions of docker desktop. I thought that the problem might be in some newer features either in docker compose or build, so I tried everything I could thought of to fix it, but still same result: I am not only getting I will stay on old version and not upgrade until this is fixed. And it's a joke that with this kind of problem they started asking for paid subscription in latest versions. |
|
Same problem - Win 11, docker v4.29.0 |
|
In my case the problem was with database volume folder from previous compose build in project directory. I deleted it, then removed mysql image and when I run after that |
|
|
and others
Description
I'm seeing this regularly on Docker Desktop v4.21.1 (Windows), running docker client on Windows.
It doesn't seem to do any harm, ddev startup continues.
Reproduce
ddev startExpected behavior
No complaints; didn't used to see this.
docker version
$ docker version Client: Cloud integration: v1.0.35 Version: 24.0.2 API version: 1.43 Go version: go1.20.4 Git commit: cb74dfc Built: Thu May 25 21:53:15 2023 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.21.1 (114176) Engine: Version: 24.0.2 API version: 1.43 (minimum version 1.12) Go version: go1.20.4 Git commit: 659604f Built: Thu May 25 21:52:17 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0docker info
Diagnostics ID
9E14D454-B129-4D1B-B987-681D1D330F62/20230720000416
Additional Info
No response
The text was updated successfully, but these errors were encountered: