deno:bin container fails because the binary is dynamically linked

[toxeus]

The deno:bin container crashes immediately because the deno binary has been dynamically linked and the required shared libraries are deliberately missing.

What you want instead is to link the deno binary statically (pretty trivial in rust) such that it's self-contained. Then, copy the statically linked deno binary into the deno:bin image. This resolves the issue.

{"msg":"exec container process (missing dynamic library?) /deno: No such file or directory","level":"error","time":"2025-07-17T05:08:21.395134Z"}

See the screenshot below for some more details

[nullish-dev]

Is there any progress on this? I'm facing the same issue. Have also tested with v2.5.4

[bartlomieju]

The deno:bin image is intentionally a minimal FROM scratch image — it's not meant to be run directly. It exists as a utility image for multi-stage builds, where other Dockerfiles copy the binary out of it:

FROM denoland/deno:bin AS bin
FROM debian:stable-slim
COPY --from=bin /deno /usr/bin/deno

All the official image variants (debian, ubuntu, alpine, distroless) use it this way. If you need a runnable container, use one of those instead (e.g. denoland/deno:latest).

Statically linking Deno is not trivial due to its dependencies (V8, etc.) and would be an upstream Deno decision.