FFFF Fix production image libc compatibility by dominicletz · Pull Request #7 · dominicletz/agentyard · GitHub
[go: up one dir, main page]
Skip to content
This repository was archived by the owner on Oct 16, 2026. It is now read-only.

Fix production image libc compatibility #7

Merged
dominicletz merged 1 commit into from
Sep 25, 2026
Merged

Fix production image libc compatibility #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .dockerignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,5 +6,12 @@ assets/node_modules
node_modules
tmp
*.log

# Runtime credentials and other local secret material stay outside the build context.
.env
.env.*
secrets/
*.secret
*.secret.*
*.pem
*.key
4 changes: 3 additions & 1 deletion Dockerfile.prod
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,9 @@ RUN mix assets.deploy \
&& mix compile \
&& mix release

FROM debian:bookworm-slim AS runner
# The official Elixir image is based on Debian trixie. Keep the release runner
# on the same libc family without carrying the Elixir build toolchain into prod.
FROM debian:trixie-slim AS runner

ENV LANG=C.UTF-8 \
MIX_ENV=prod \
Expand Down
Loading
0