Docker / Docker

Docker 29.4.1 Daemon dies with panic: crypto requested hash function unavailable

Fix Docker daemon crash caused by missing Go crypto hash function — containers become unmanageable after unexpected daemon death. Includes evidence for Docker troubleshooting demand.

Source-backed Last updated May 17, 2026 1 source Needs local verification

Category: Docker
Error signature: panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime)
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 17, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Docker, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime) is a Docker failure pattern reported for developers trying to fix docker daemon crash caused by missing go crypto hash function — containers become unmanageable after unexpected daemon death.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue moby/moby#52578: Docker daemon v29.4.1 crashes with panic in go-digest.Algorithm.Hash(). Stack trace points to Go stdlib crypto package. 9 comments, created 2026-05-07. Production-critical runtime crash with clear stack trace. Known regression in 29.4.x series.

Common causes

GitHub issue moby/moby#52578: Docker daemon v29.4.1 crashes with panic in go-digest.Algorithm.Hash(). Stack trace points to Go stdlib crypto package. 9 comments, created 2026-05-07. Production-critical runtime crash with clear stack trace. Known regression in 29.4.x series.

Quick fixes

Confirm the exact error signature matches panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime).
Check the Docker account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime) exactly before applying the quick fix.
Compare the failing environment with Docker versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime) mean in Docker?

panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime) indicates the workflow described by "Docker 29.4.1 Daemon dies with panic: crypto requested hash function unavailable" failed in a Docker context. Start by confirming the exact signature and the component that emitted it.

What should I check first for panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime)?

Check whether this cause matches your environment: GitHub issue moby/moby#52578: Docker daemon v29.4.1 crashes with panic in go-digest.Algorithm.Hash(). Stack trace points to Go stdlib crypto package. 9 comments, created 2026-05-07. Production-critical runtime crash with clear stack trace. Known regression in 29.4.x series.

Is the panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime) guidance source-backed?

The "Docker 29.4.1 Daemon dies with panic: crypto requested hash function unavailable" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime)?

For "Docker 29.4.1 Daemon dies with panic: crypto requested hash function unavailable", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging panic: crypto: requested hash function #0 is unavailable (Docker daemon crash, Go runtime)?

For "Docker 29.4.1 Daemon dies with panic: crypto requested hash function unavailable", collect the failing Docker command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.