hob Posts - Deno

hob

•Created by hob on 3/15/2025 in #help

high memory usage using compiled binary in docker

# Build stage
FROM denoland/deno:2.2.3 AS builder
WORKDIR /app
COPY . .
RUN deno task build
RUN deno compile \
  --allow-read --allow-write --allow-net --allow-env \
  --include dist/ --output candiru main.ts

# Runtime stage
FROM debian:bookworm-slim
WORKDIR /app
COPY --from=builder /app/candiru .
EXPOSE 3000
CMD ["/app/candiru"]

# Build stage
FROM denoland/deno:2.2.3 AS builder
WORKDIR /app
COPY . .
RUN deno task build
RUN deno compile \
  --allow-read --allow-write --allow-net --allow-env \
  --include dist/ --output candiru main.ts

# Runtime stage
FROM debian:bookworm-slim
WORKDIR /app
COPY --from=builder /app/candiru .
EXPOSE 3000
CMD ["/app/candiru"]

I'm fairly new to docker. I tried something similar to what's in the docs here, with deno task build in the build stage, before trying to run the compiled version of my app. Memory usage is very high (800mb) in both versions. Running the compiled version of the app on my machine only uses around 70mb. How can I decrease the memory usage of the docker container? I'd love to get it under 200mb. Any help would be greatly appreciated! link to my repo for context if that helps: https://github.com/candirugame/candiru

15 replies