Repository navigation
Docker Engine Crashing #286
Description
Description
Docker engine seems to be crashing randomly, so far overnight. It's running on Kubuntu Desktop, Docker Desktop 4.40.0 and Docker version 28.1.1, build 4eba377.
When it crashes I get this error message:
running engine: engine linux/qemu failed to run: running VM: running virtiofsd for /home: signal: bad system call (core dumped)
I can't seem to find much on this online, though. Related to the file system but I can't seem to find any further logs giving more clues than that.
Reproduce
Leave Docker containers running, sometimes after a day or two I wake up in the morning to find docker engine crashed. Unfortunately I don't have more consistent info.
Expected behavior
Not crashing.
docker version
Client: Docker Engine - Community
Version: 28.1.1
API version: 1.48 (downgraded from 1.49)
Go version: go1.23.8
Git commit: 4eba377
Built: Fri Apr 18 09:52:14 2025
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.40.0 (187762)
Engine:
Version: 28.0.4
API version: 1.48 (minimum version 1.24)
Go version: go1.23.7
Git commit: 6430e49
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.26
GitCommit: 753481ec61c7c8955a23d6ff7bc8e4daed455734
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0docker info
Client: Docker Engine - Community
Version: 28.1.1
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.1.3
Path: /usr/lib/docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.22.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
cloud: Docker Cloud (Docker Inc.)
Version: 0.2.20
Path: /usr/lib/docker/cli-plugins/docker-cloud
compose: Docker Compose (Docker Inc.)
Version: v2.34.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: /usr/lib/docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.6
Path: /usr/lib/docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /usr/lib/docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /usr/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.17.0
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Containers: 12
Running: 10
Paused: 0
Stopped: 2
Images: 21
Server Version: 28.0.4
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
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 753481ec61c7c8955a23d6ff7bc8e4daed455734
runc version: v1.2.5-0-g59923ef
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.10.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 29.37GiB
Name: docker-desktop
ID: c8b8edaf-da98-4fdb-9d18-c36e03c0235e
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=unix:///home/wpx/.docker/desktop/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
::1/128
127.0.0.0/8
Live Restore Enabled: false
WARNING: DOCKER_INSECURE_NO_IPTABLES_RAW is set
WARNING: daemon is not using the default seccomp profileDiagnostics ID
054161C4-1F61-441E-96CA-7828F8E26100/20250505154404
Additional Info
No response
Activity
CPioGH2002 commentedon Jun 7, 2025
Did you check the logs after this event took place?
The
journalctlcommand has a lot to offer in that regard, but you can also use GUI-based tools like KSytemLog. In the time leading up the Docker Engine crash, perhaps start with checking even the normal entries, not just "warning" or "error" ones.If you remove all personal data, you can also pack the logs in a spoiler or attach them as files. Maybe the devs can find something of note.
Side note: Since I also happen to have an open issue and also one which concerns virtiofsd, I'd like to recommend manually updating the binary since, in my case (using Docker Desktop for Linux), it shipped with an outdated one. The current virtiofsd release can be found here: https://gitlab.com/virtio-fs/virtiofsd/-/releases
Rathlord commentedon Jun 7, 2025
Thanks for the response- I did try to check the logs, not sure I found everything but I couldn't find much useful info. It's a great recommendation for virtiofsd, unfortunately I got frustrated and just deleted Docker Desktop and moved to CLI and Portainer for managing my containers, so I can't check now.
CPioGH2002 commentedon Jun 7, 2025
Makes sense since the issue of yours wasn't resolved and if Docker (non-Desktop) now works for you, your system setup wasn't to blame in the first place.
I might end up using the same combo since I haven't heard from the devs so far. Anyhow, thanks for the feedback. :-)
meet-bhalodiya-iverve commentedon Aug 28, 2025
Its really frustating and is happening to me as well docker engine keeps on crashing randomly and the containers dont respond at all seems like the option i have is to move to cli itself, I have been using docker desktop from last 2-3 years but as i got the new PC I installed the latest version and have been facing issues since then.
it just freezes like this and there is not way to get it running but restart, even then after a few mintues it crashes so all i have to do the whole day is either keep on restrating the docker engine or downgrade the version and try again (its not working properly in any v28.x.x)
tuan0919 commentedon Jun 13, 2026
Facing the same issue, really frustating when using Docker Desktop nowadays. It keep randomly crashes and get no helps after tracing logs from journalctl itself, guess gotta migrate to CLI asap