Uh oh!
There was an error while loading. Please reload this page.
fix: stage runtime-access.sql at the recipe context root (#68) - #69
Merged
antoinetoussaint-byte merged 1 commit intoAug 23, 2026
Conversation
The build recipe rendered runtime-access.sql into builder/, but the CLI treats the Dockerfile's builder/ directory as recipe metadata and drops it from the staged build context, so `COPY builder/runtime-access.sql` failed to resolve. Render it at the context root beside migrations/ (which the CLI does stage) and COPY it from there. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
antoinetoussaint-byte
deleted the
issue-68-0-0-125-breaks-container-build-builder-runtime
branch
August 23, 2026 22:41
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes#68.
Summary
builder/directory holds the Dockerfile. The CLI treats that Dockerfile directory as recipe metadata and drops it from the staged build context, so the generatedCOPY builder/runtime-access.sqlcould no longer resolve its checksum and every runtime-access build failed.migrations/survived because it is a sibling ofbuilder/, not inside it.runtime-access.sqlat the build-context root besidemigrations/— the directory the CLI does stage — andCOPYs it from there.builder/now carries only the Dockerfile (read via-f), matching theSingleImageBuildPlanconvention the Go/Rust runners already rely on. The legacy in-process build path is kept consistent (same context-root layout, same shared Dockerfile).Test plan
go test ./...(includesTestBootstrapImageBuildsWhenDockerOmitsTargetArchitecture, which builds a real image via BuildKit with the newCOPY runtime-access.sql)go vet ./...TestBuildEmitsRecipeToOutputDirectorynow assertsruntime-access.sqlsits at the context root and is absent frombuilder/🤖 Generated with Claude Code