service fs failed: injecting event blocked for 60s
Description
This is a cross-post from https://github.com/docker/for-mac/issues/7759 as I've been experiencing the same issue on windows for a couple of weeks now.
Reproduce
I get it from running single container with a run command with a volume mapped under it.
Expected behavior
the engine to not die
docker version
❯ docker version
Client:
Version: 28.4.0
API version: 1.51
Go version: go1.24.7
Git commit: d8eb465
Built: Wed Sep 3 20:59:40 2025
OS/Arch: windows/amd64
Context: desktop-linux
Server: Docker Desktop 4.47.0 (206054)
Engine:
Version: 28.4.0
API version: 1.51 (minimum version 1.24)
Go version: go1.24.7
Git commit: 249d679
Built: Wed Sep 3 20:57:37 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
❯ docker info
Client:
Version: 28.4.0
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.9.11
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.28.0-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
cloud: Docker Cloud (Docker Inc.)
Version: v0.4.29
Path: C:\Program Files\Docker\cli-plugins\docker-cloud.exe
compose: Docker Compose (Docker Inc.)
Version: v2.39.4-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.42
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.2.0
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.31
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
mcp: Docker MCP Plugin (Docker Inc.)
Version: v0.21.0
Path: C:\Users\meza\.docker\cli-plugins\docker-mcp.exe
model: Docker Model Runner (Docker Inc.)
Version: v0.1.41
Path: C:\Program Files\Docker\cli-plugins\docker-model.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.18.3
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 16
Server Version: 28.4.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: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Discovered Devices:
cdi: docker.com/gpu=webgpu
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
runc version: v1.2.5-0-g59923ef
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.10.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 7.751GiB
Name: docker-desktop
ID: 223007b2-4d98-4937-a5e6-819dcb86e06c
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
::1/128
127.0.0.0/8
Live Restore Enabled: false
Diagnostics ID
620D4D01-AF5A-479C-8E16-B304E1923591/20251002224054
Additional Info
No response
@bsousaa 4.48.0 seems to have fixed it, but still keeping an eye on it
Yes, we have positive feedback in the for-mac issue tracker 👍
I am running into a different issue with this release but I'm not sure if it's related. I get kicked out of the container and even though it is running with --rm, Docker Desktop shows that the container is running. I can't then stop it or delete it without restarting the engine. Attempting to run a new instance gives me a 500 error until the engine is restarted.
› time="2025-10-13T11:40:54+01:00" level=error msg="error waiting for container: unexpected EOF"
Diagnostics ID: 620D4D01-AF5A-479C-8E16-B304E1923591/20251013104733
Not sure if this is related but it feels like a similar issue with a different symptom
Same problem on 4.49 / Windows
Diagnostics Id: DB336E3C-FB97-421A-BB61-F7CCC2F6F889/20251024163112
Before updating to 4.49 this problem showed up couple of times this month, after updating today it showed up twice in 5h. (the machine was idle with dozen of running containers)
Still occurring on 4.50 / Windows (Hyper-V) Diagnostics ID: 6323D260-D33A-4747-8FF2-7F90AFF52582/20251114085003
Shows up ~3 times per work day, no particular process triggers this. Seems to occur more often when docker containers are idle (when I don't make REST API calls to back-end container) Requires full docker restart to fix. Full re-install does not solve the issue.
Error started to occur after updating from 4.34 to 4.48.
4.51 seems to be working for me, give it a go!
Spoke too soon. However it doesn't even crash, just my container becomes unresponsive.
Still occuring in 4.52
Still occuring in 4.53. Is there any progress on this? Is this even being investigated?
@threatv yes, this is being investigated
Same issue here on a Mac Mini Sequoia. System goes unresponsive, and I can hear the fans going full speed. I have the internal SSD and a External HD mounted on some containers.
Issue is happening on a few versions, I'm on 4.53 now
Still happening on 4.55 trying to gather diagnostics also fails.
Reported similar error on Ubuntu: https://github.com/docker/desktop-linux/issues/314
It happens to me multiple times a day... Diagnostic ID: 16E0D209-6118-4DE7-9EA4-0840A654E823/20260117213711
Seen on debian as well https://github.com/docker/desktop-linux/issues/301
Still happening in 4.58.0 Diagnostic ID: 6323D260-D33A-4747-8FF2-7F90AFF52582/20260202103118