denoland
deno_docker
Dockerfile

Latest dockerfiles and images for Deno - alpine, centos, debian, ubuntu

Last updated Jul 8, 2026
1.0k
Stars
114
Forks
18
Issues
0
Stars/day
Attention Score
91
Language breakdown
No language data available.
Files click to expand
README

deno_docker

Docker files for Deno published on Docker Hub and GHCR:

  • Alpine Linux: denoland/deno:alpine
  • Debian: denoland/deno:debian (default)
  • Distroless: denoland/deno:distroless
  • Ubuntu: denoland/deno:ubuntu
  • Only the binary: denoland/deno:bin
Images are available from both registries:
docker pull denoland/deno:2.9.2        # Docker Hub
docker pull ghcr.io/denoland/deno:2.9.2 # GHCR

Run locally

To start the deno repl:

$ docker run -it denoland/deno:2.9.2 repl

To shell into the docker runtime:

$ docker run -it denoland/deno:2.9.2 sh

To run main.ts from your working directory:

$ docker run -it -p 1993:1993 -v $PWD:/app denoland/deno:2.9.2 run --allow-net /app/main.ts

Here, -p 1993:1993 maps port 1993 on the container to 1993 on the host, -v $PWD:/app mounts the host working directory to /app on the container, and --allow-net /app/main.ts is passed to deno on the container.

As a Dockerfile

FROM denoland/deno:2.9.2

The port that your application listens to.

EXPOSE 1993

WORKDIR /app

Cache dependencies as a layer (re-run only when package.json changes).

COPY package.json . RUN deno install

These steps will be re-run upon each file change in your working directory:

COPY . .

Compile the main app so that it doesn't need to be compiled each startup/entry.

RUN deno cache main.ts

Prefer not to run as root.

USER deno

CMD ["run", "--allow-net", "--allow-read", "--allow-env", "main.ts"]

and build and run this locally:

$ docker build -t app . && docker run -it -p 1993:1993 app

Using your own base image

If you prefer to install deno in your own base image, you can use the denoland/deno:bin to simplify the process.

FROM ubuntu
COPY --from=denoland/deno:bin-2.9.2 /deno /usr/local/bin/deno

Running on Google Cloud Run(GCR)

Due to conflicts with google cloud run caching mechanism it's required to use different path for DENO_DIR in your Dockerfile.
# set DENO_DIR to avoid conflicts with google cloud
ENV DENODIR=./.denocache

Without it GCR instance will try to download deps every time. When running with --cached-only you will get Specified not found in cache.

(optional) Add deno alias to your shell

Alternatively, you can add deno command to your shell init file (e.g. .bashrc):

deno () {
  docker run \
    --interactive \
    --tty \
    --rm \
    --volume $PWD:/app \
    --volume $HOME/.deno:/deno-dir \
    --workdir /app \
    denoland/deno:2.9.2 \
    "$@"
}

and in your terminal

$ source ~/.bashrc
$ deno --version
$ deno run ./main.ts

See example directory.

Note: Dockerfiles provide a USER deno and DENO_DIR is set to /deno-dir/ (which can be overridden).

_If running multiple Deno instances within the same image you can mount this directory as a shared volume._

🔗 More in this category

© 2026 GitRepoTrend · denoland/deno_docker · Updated daily from GitHub