docker: dockerd randomly segfaults

[ARandomPig]

Nixpkgs version

• Unstable (25.05)

Describe the bug

When using docker on my personal server I got some errors like this :

failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF

this problems happens randomly when using docker and I can't find anything on internet about it.

Steps to reproduce

I don't really know what causes this. this problem just happens when using docker normally, and it happens quite often (I can make it happen with a 2 minutes docker compose build).

Expected behaviour

I would like it to not crash, that would be nice.

Screenshots

No response

Relevant log output

Mar 24 19:19:46 server systemd[1]: Started Docker Application Container Engine.
Mar 24 19:21:21 server systemd-coredump[3272]: [🡕] Process 1884 (dockerd) of user 0 dumped core.

                                               Module libcap.so.2 without build-id.
                                               Stack trace of thread 3131:
                                               #0  0x000055c99fc7bf98 runtime.mallocgcSmallNoscan (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x183af98)
                                               #1  0x000055c99fcdd919 runtime.mallocgc (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x189c919)
                                               #2  0x000055c99fce2dc9 runtime.growslice (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x18a1dc9)
                                               #3  0x000055c99fcda256 runtime.vgetrandomPutState (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x1899256)
                                               #4  0x000055c99fcad205 runtime.mexit (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x186c205)
                                               #5  0x000055c99fcacebf runtime.mstart0 (/nix/store/cl8lra4h1d3a5p52k8dkjnffbjwiv6d7-moby-27.5.1/libexec/docker/dockerd + 0x186bebf)
                                               ELF object binary architecture: AMD x86-64
Mar 24 19:21:21 server systemd[1]: docker.service: Main process exited, code=dumped, status=11/SEGV
Mar 24 19:21:21 server systemd[1]: docker.service: Failed with result 'core-dump'.
Mar 24 19:21:21 server systemd[1]: docker.service: Consumed 48.043s CPU time, 6.8G memory peak, 142.2M read from disk, 6.7G written to disk, 2G incoming IP traffic, 8.3M outgoing IP traffic.

Additional context

No response

System metadata

• system: "x86_64-linux"
• host os: Linux 6.12.19, NixOS, 25.05 (Warbler), 25.05.20250322.1e5b653
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.24.12
• nixpkgs: /nix/store/fnc4632ncr5k5la19gp2gb255dx8pi9x-source

Notify maintainers

@offlinehacker
@vdemeester
@periklis
@teutat3s

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[ARandomPig]

just tested docker_25 and docker_26, they have the same problem

[anthonymoran]

Having the same issue. Occurs when I am doing a docker compose pull.

Mar 25 15:08:00 server systemd-coredump[75660]: [🡕] Process 33642 (dockerd) of user 0 dumped core.

                Module libcap.so.2 without build-id.
                Stack trace of thread 37375:
                #0  0x000055faa3cb5f98 runtime.mallocgcSmallNoscan (/nix/store/cl8lra4h1d>
                #1  0x000055faa3d17919 runtime.mallocgc (/nix/store/cl8lra4h1d3a5p52k8dkj>
                #2  0x000055faa3d1cdc9 runtime.growslice (/nix/store/cl8lra4h1d3a5p52k8dk>
                #3  0x000055faa3d14256 runtime.vgetrandomPutState (/nix/store/cl8lra4h1d3>
                #4  0x000055faa3ce7205 runtime.mexit (/nix/store/cl8lra4h1d3a5p52k8dkjnff>
                #5  0x000055faa3ce6ebf runtime.mstart0 (/nix/store/cl8lra4h1d3a5p52k8dkjn>
                ELF object binary architecture: AMD x86-64
Mar 25 15:08:00 server systemd[1]: docker.service: Consumed 2min 16.896s CPU time, 12.9G memory peak, 2.6M read from disk>
Mar 25 15:08:02 server systemd[1]: docker.service: Scheduled restart job, restart counter is at 5.

host os: Linux 6.12.19 #1-NixOS SMP PREEMPT_DYNAMIC Thu Mar 13 12:02:20 UTC 2025 x86_64 GNU/Linux

[nadir-ishiguro]

I noticed what I think is the same issue for a few days now. Only noticed it after I set a number of my services not to restart: no for unrelated reasons. I suspect this might have happened before without me noticing.