Fix production image libc compatibility by dominicletz · Pull Request #7 · dominicletz/agentyard

dominicletz · 2026-09-25T23:19:31Z

Summary

Run the release on debian:trixie-slim, matching the Debian/libc family used by the current official Elixir builder image.
Preserve the slim non-root runtime, healthcheck dependencies, and migrate-then-start entrypoint.
Keep environment files, secret material, build output, dependencies, and Git metadata out of the Docker build context; production credentials remain runtime-only.

Build the image with docker build -f Dockerfile.prod -t agentyard:prod ..
Run it briefly with the deployment environment and database available, then confirm the Beam VM starts and logs contain no GLIBC_2.38 errors.
Verify the container continues to run as the non-root agentyard user and that the healthcheck can reach the app with curl.

GHCR package visibility is handled separately and is not part of this change.

Co-authored-by: Dominic Letz <dominicletz@users.noreply.github.com>

Fix production runtime libc compatibility

f9e04c5

Co-authored-by: Dominic Letz <dominicletz@users.noreply.github.com>

dominicletz marked this pull request as ready for review September 25, 2026 23:21

dominicletz merged commit 0c546f6 into main Sep 25, 2026
1 check passed

dominicletz deleted the cursor/match-prod-runtime-libc-9ac5 branch September 25, 2026 23:21