You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix: deriving stack.toml from the new run image information #1788 - $ docker run -it --rm test-builder cat /cnb/stack.toml sometimes shows image = "cnbs/sample-stack-run:jammy" and sometimes shows [run-image]\nimage = "cnbs/sample-stack-run:jammy" - we think the former is correct; the difference shows up depending on how base information is specified in builder.toml ([stack] only, [run] only, or both)
We need to provide -run /layers/run.toml to the detector Actually, we don't need to do this. The detector is running in the context of the builder image (not the lifecycle image), so run.toml is already present at the default location of /cnb/run.toml
The text was updated successfully, but these errors were encountered:
Summary
Similar to buildpacks/lifecycle#1057, this issue is meant to capture small bugs to be fixed before we can ship the next pack.
TODO:
In flight:
ERROR: validating buildpacks: buildpack samples/[email protected] does not support target: (linux amd64, @)
$ docker run -it --rm test-builder cat /cnb/stack.toml
sometimes showsimage = "cnbs/sample-stack-run:jammy"
and sometimes shows[run-image]\nimage = "cnbs/sample-stack-run:jammy"
- we think the former is correct; the difference shows up depending on how base information is specified in builder.toml ([stack]
only,[run]
only, or both)Done:
We need to provideActually, we don't need to do this. The detector is running in the context of the builder image (not the lifecycle image), so run.toml is already present at the default location of /cnb/run.toml-run /layers/run.toml
to the detectorThe text was updated successfully, but these errors were encountered: