Skip to content

Support artifact-only frontend exports - #1

Draft
mabadir wants to merge 1 commit into
flightcontrol/v0.29.0-cache-importsfrom
codex/railpack-static-output
Draft

Support artifact-only frontend exports#1
mabadir wants to merge 1 commit into
flightcontrol/v0.29.0-cache-importsfrom
codex/railpack-static-output

Conversation

@mabadir

@mabadir mabadir commented Jul 10, 2026

Copy link
Copy Markdown

Summary

  • add an export-path frontend build argument
  • return a scratch state containing only the requested directory when it is set
  • document Flightcontrol's frontend patches and immutable image release flow

Why

Flightcontrol static builds currently export and load Railpack's complete runtime image only to copy one static artifact directory back out. BuildKit's local exporter cannot help by itself because the Railpack gateway frontend returns the complete deploy filesystem.

This opt-in frontend behavior narrows the returned LLB state to the requested artifact directory, allowing Flightcontrol to use --output type=local without serializing the runtime image and its parent layers.

Validation

  • go test ./buildkit
  • golangci-lint run (0 issues)
  • go vet ./...
  • go mod verify
  • go test -short ./... (all packages pass except four pre-existing PHP dynamic-image snapshots whose patch versions moved: 8.2.31→8.2.32 and 8.4.22→8.4.23)

Rollout

After merging, publish the frontend as public.ecr.aws/a8z1i1r2/railpack-frontend:v0.29.0-fc2. The coordinated Flightcontrol PR is flightcontrolhq/flightcontrol#6647 and remains draft until that immutable image exists.

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