use paketobuildpacks for custom builder validation #246
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.
Cloud Run button supports supplying a custom builder, rather than using the default "gcr.io/buildpacks/builder".
The buildpacks-builder test was failing due to Heroku buildpacks no longer having a tagged latest (presumably this worked before), and have also have been deprecated, replaced with heroku/builder. However, both of these versions are not compatible with the version of pack being used (e.g.
ERROR: failed to build: Builder 'heroku/builder:22' is incompatible with this version of pack
)So instead, replace the use of heroku with another buildpack. From the
pack builder suggest
output,paketobuildpacks/builder
is an option. Using the:full
image since the sample application used is PHP, and the:tiny
version doesn't support this.