Starting workspaces from a Dockerfile #21187
Labels
area/dashboard
area/devworkspace-operator
kind/enhancement
A feature request - must adhere to the feature request template.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
roadmap/3-months
Epics that are planned to complete in the short term (within 3 months)
severity/P1
Has a major impact to usage or development of the system.
sprint/current
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
image.imageName
and thecontainer.image
with a valid image reference (registry/org/name:tag
) and the defaultregistry
,org
andtag
should be configurable at the CheCluster level.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
The text was updated successfully, but these errors were encountered: