Starting workspaces from a Dockerfile

[l0rd]

Is your enhancement related to a problem? Please describe

If a developer wants to use a custom image from a Dockerfile he has to 1) pre-build it 2) push it to a registry 3) update the devfile to reference the just published image. This is bad UX.

Describe the solution you'd like

• Support image components to use Dockerfile as component spec devfile/devworkspace-operator#1036
• If needed, Eclipse Che Dashboard should replace the image.imageName and the container.image with a valid image reference (registry/org/name:tag) and the default registry, org and tag should be configurable at the CheCluster level.
• A new Che URL parameter dockerfilePath should be supported. If this parameter is provided, Che should generate a DevWorkspace using the defaultComponents+ a new image component referencing the Dockerfile. If this parameter is provided Che should ignore any devfile at the root of the git repo.

Describe alternatives you've considered

Similar to image-puller, we could implement a service that would be responsible for the build of the images

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[l0rd]

/remove-lifecycle stale

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.