Repository navigation
build(docker): slim prod image (1.08GB → 390MB) - #2
Merged
Merged
Conversation
- drop what pnpm prune --prod keeps but the runtime never loads: the prisma CLI (a resolved peer of @prisma/client, pulling in studio, engines, pglite, typescript, effect, react) and the non-postgres query compilers - drop libvips-dev from the prod stage: nothing in gatherly uses sharp - one RUN for apt upgrade + npm uninstall - no build toolchain in the builder: no native modules to compile - ignore *.tsbuildinfo: a stale local one made nest build skip emitting dist/main.js in local image builds Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fileharbor): afterpnpm prune --prod, remove the prisma CLI and what it drags in as a resolved peer of@prisma/client(@prisma/studio-core,@prisma/engines,@prisma/dev,@electric-sql/pglite,typescript,effect,react,react-dom), plus the Prisma query compilers for cockroachdb, mysql, sqlite, sqlserver. Migrations aren't run from this image.libvips-dev(and the hundreds of MB of-devpackages it pulls) removed from the prod stage. Nosharp/vipsinpackage.json,pnpm-lock.yamlorsrc/.apt-get upgradeandnpm uninstall -g npm corepackin oneRUN, like bastion.build-essential python3 curl ca-certificates gcc g++ makeremoved from the builder. No prod dependency ships abinding.gypor.node; the build passes without them..dockerignoregets*.tsbuildinfo: a leftover localtsconfig.build.tsbuildinfowas copied into the context, so incrementaltscskipped emitting and the image had nodist/main.js(local builds only; CI's clean checkout has no buildinfo). Same rule as the template.docker image ls)--target prodVerified: no
require()of the removed packages in the image'sdist/; on a local Postgres with the migrations applied, the container starts andGET /health/readyreturns 200 (database: up; Bastion unreachable, logged and retried as designed).🤖 Generated with Claude Code