Make it possible to customise images for dev containers

In this issue I want to discuss the way in which we would have an ability to customise images used in dev containers.

Right now the whole list of images which are used in dev containers is located in https://github.com/eclipse/che-devfile-registry/blob/master/arbitrary-users-patch/base_images and we don’t have a good way to patch/customise only one of them, for example, install yarn into registry.centos.org/che-stacks/centos-nodejs or unset some env in che-java11-maven.

I suggest to move all dockerfiles from che-devfiles-registry to https://github.com/che-dockerfiles as @benoitf did for dockerfiles which are used in che remote plugins. For this we’d need to create a repository for each of them in https://github.com/che-dockerfiles and add github actions to build and publish. In that case in che-devfile-registre we will have only devfiles.

WDYT @benoitf @amisevsk @tsmaeder @l0rd

[tsmaeder]

Update the arbitrary UID patch to use the che-dockerfiles images as a base, where necessary

I would do it the other way around, t.b.h: the arbitrary-users-patch takes community images and makes them usable on OpenShift. These OS-capable images can serve as a base for multiple other images, for example one including yarn, but maybe we have a second one that uses a gulp, for example.

[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.