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
See #21483 for an example of a user providing an image name that causes a failure in the CNB builder that is difficult to diagnose (upper-case characters in the image name):
[INFO] > Running creator
[INFO] [creator] ERROR: failed to all tags must have the same registry as the exported image: could not parse reference: docker.io/library/SchedulePolling:1.2
If we better understood the rules for an image reference, Boot could do some validation of the image name before invoking the builder to give a better user experience. For comparison, the pack CLI gives a more concise error message, although still missing the details of what isn't acceptable about the image name:
$ pack build docker.io/library/DemoProject:1.0 --builder gcr.io/paketo-buildpacks/builder:base-platform-api-0.3 --path build/libs/demo-0.0.1-SNAPSHOT.jar
ERROR: invalid image name 'docker.io/library/DemoProject:1.0': could not parse reference: docker.io/library/DemoProject:1.0
The text was updated successfully, but these errors were encountered:
philwebb
changed the title
Consider validating an image reference before passing it to a CNB builder
Validate the image reference before passing it to a CNB builder
Jun 11, 2020
philwebb
changed the title
Validate the image reference before passing it to a CNB builder
Image references passed to a CNB builder are not validated
Jun 11, 2020
Rename `ImageReferenceParser` to `Regex` and remove state. The regular
expressions are now used directly by the `ImageName` and
`ImageReference` classes with the values accessed directly from the
`Matcher`.
See gh-21495
See #21483 for an example of a user providing an image name that causes a failure in the CNB builder that is difficult to diagnose (upper-case characters in the image name):
If we better understood the rules for an image reference, Boot could do some validation of the image name before invoking the builder to give a better user experience. For comparison, the
pack
CLI gives a more concise error message, although still missing the details of what isn't acceptable about the image name:The text was updated successfully, but these errors were encountered: