Description of problem:
When I use the sample repository from the Devfile Import Form, the pod never comes up
Please see https://github.com/openshift/console/issues/8729
Could verify that the sample could not start successful.
How should we detect the "build guidance" image (by name, by attributes.tool or by container.image) and what should we do with it?
Within the boundary of the devfile 2.0 spec, ODC can currently use the container that has the attribute:
to identify. We added that explicitly for the current ODC support. By the time we go to devfile 2.2 in the future, we'll have a specific outer loop definition that ODC can use to remove that ODC specific attribute.
@email@example.com adding to Elson's comment, https://github.com/redhat-developer/devfile-sample/blob/master/devfile.yaml#L9-L17 this "build guidance" devfile component only defines an endpoint that is valuable to ODC. ODC uses build config to build the application and pushes it to the OpenShift registry. So the container image to be used is from the resulting build. This UX will be improved with the actual devfile spec for outerloop targeted for devfile 2.2.0 where the user can specify the image name in devfile they want the build config to output to. So presently, ODC just uses the container image built from the build config and uses the devfile "build guidance" endpoint to create a service. But right now, it creates an invalid container with the invalid "build guidance" image from the devfile.
FWIW, I have hit this on the dev sandbox now that it has moved up to 4.7.
The pod starts successfully
verified on 4.8.0-0.nightly-2021-04-30-102231