-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
builds-1.6
-
None
-
1
-
False
-
-
False
-
-
-
1
-
Builds Sprint #36, Builds Sprint #37
-
2
Description of problem:
When trying to build a sample NodeJS application with the Paketo Jammy buildpack builders, they consistently fail on the analyze step because run metadata is missing.
Specifying a run-image appears to be required, which is not well documented upstream with Paketo or CNB docs.
Workaround: Use the pinned builder image and run image referenced in the documentation
Prerequisites (if any, like setup, operators/versions):
Shipwright v0.17.0
Steps to Reproduce
# Create a build with the Red Hat buildpacks strategy for a nodeJS app, setting the `cnb-builder-image` parameter to docker.io/packetobuildpacks/builder-jammy-base:latest
- Run the build
Actual results:
Build fails on analyze step because it is missing run information:
*** Pod "quizap-frontend-build-wcj9x-6ftkp-pod", container "step-analyze": *** Starting analyzer... Parsing inputs... No run metadata found at path "/cnb/run.toml" [31;1mERROR: [0mfailed to resolve inputs: -run-image is required when there is no run metadata available
Expected results:
Analyzer step succeeds
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Shipwright v0.17.0
KIND cluster running v1.34.0 control plane
Additional info (Such as Logs, Screenshots, etc):
- relates to
-
BUILD-1663 RFE: Use Buildpacks Without Runtime Image
-
- New
-