Closed cmoulliard closed 4 months ago
The error repiorted was due to a wrong image passed to the lifecyle. This is fixed
We are nevertheless getting a new error:
ERROR: stat /kaniko: no such file or directory
Stream closed EOF for default/buildpack-quarkus-buildrun-55qpt-5dlxf-pod (step-extender)
ERROR: stat /kaniko: no such file or directory
Fixed after adding the missing volume mounting: /kaniko
hmhmh. We got now this error may be because we don't specify the output image name correctly
Starting extender...
Parsing inputs...
Ensuring privileges...
Executing command...
ERROR: failed to extend build image: getting build image to extend: failed to get digest for reference '': a digest must contain exactly one '@' separator (e.g. registry/repository@digest) saw:
Stream closed EOF for default/buildpack-quarkus-buildrun-fsnvj-5wtw5-pod (step-extender)
Idea about the cause of this error ? @BarDweller
ERROR: failed to extend build image:
Fixed as the shipwright restore step was missing the build-image param:
- name: restore
image: $(params.CNB_BUILDER_IMAGE)
imagePullPolicy: Always
command: ["/cnb/lifecycle/restorer"]
args:
- "-log-level=$(params.CNB_LOG_LEVEL)"
- "-build-image=$(params.CNB_BUILD_IMAGE)"
Issue
The shipwright pod fails during execution of a buildpack step:
build-an-push
This error is reported by the following java buildpack:
Versions:
Shipwright has been installed on a kind cluster and build created using the following resources: https://github.com/redhat-buildpacks/testing/tree/617bcbec9af7551b4995760bfbb962c2aa5916cf/k8s/shipwright/unsecured
Pod YAML: https://gist.github.com/cmoulliard/0795233fe6c87d225cf85b9c3e6c8765