Skip to content

Fix fly Docker build for injected workspace packages - #497

Merged
mjackson merged 1 commit into
mainfrom
mjackson/fix-fly-docker-workspace
Aug 26, 2026
Merged

mjackson merged 1 commit into
mainfrom
mjackson/fix-fly-docker-workspace

Conversation

@mjackson

Copy link
Copy Markdown
Member

Every fly deploy has failed since inject-workspace-packages was enabled (f0354be): the Docker build only copied the unpkg-files and unpkg-worker manifests, so the lockfile's injected file: entries could not install and the post-build injected-deps sync hit ENOENT. This copies all workspace manifests, bumps the image's pnpm to match packageManager (10.15.0), and scopes the image build to unpkg-worker + unpkg-files. Verified by a successful staging deploy of unpkg-files with this Dockerfile.

inject-workspace-packages requires every workspace manifest to be
present for the lockfile's injected file: entries to install, and
syncInjectedDepsAfterScripts needs the injected copies to exist when
build output syncs. The image only copied two manifests, so every fly
deploy since injection was enabled failed during pnpm run build. Copy
all workspace manifests, match the packageManager pnpm version, and
scope the build to the packages the image ships.
@mjackson
mjackson merged commit 78c08ae into main Aug 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant