[codex] Fix Docker pnpm frozen installs#28
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
.npmrcinto the Docker install layers beforepnpm install --frozen-lockfileruns..npmrcthere too.Root Cause
PR #27 added
.npmrcwithauto-install-peers=false, and the lockfile now recordssettings.autoInstallPeers: false. The Dockerfiles copiedpackage.json,pnpm-lock.yaml,pnpm-workspace.yaml, andturbo.json, but not.npmrc, so pnpm used its default peer config inside Docker and rejected the frozen install withERR_PNPM_LOCKFILE_CONFIG_MISMATCH.Validation
docker build -f Dockerfile.server --target builder -t openfacilitator-server-builder-test .docker build -f Dockerfile.dashboard --target builder -t openfacilitator-dashboard-builder-test .turbo lint