Patrick Titzler

Transferring the issue to elyra-ai/elyra.

Absolutely! We do publish an official Elyra container image based on the files in https://github.com/elyra-ai/elyra/tree/master/etc/docker/elyra that you could use as a baseline. Feel free to open an issue if you...

Opened https://github.com/elyra-ai/elyra/issues/1350 to improve the content for custom Elyra container images

I should probably mention that Elyra can be installed as part of [Open Data Hub](https://opendatahub.io/) on Red Hat OpenShift: https://elyra.readthedocs.io/en/latest/recipes/deploying-elyra-with-opendatahub.html

I turns out (my apologies) that container images built using https://github.com/elyra-ai/elyra/blob/master/etc/docker/elyra/Dockerfile won't work on RHOS. We've still got some work to do documenting how we are building the image for...

> I can't seem to find the "local" runtime option. To use the local runtime you must create pipelines using the generic pipeline editor:  When you click "run" the...

Some background information about our container images that might be helpful in this context. Both, the `elyra` and the `kf-notebook` container images (See the directories in https://github.com/elyra-ai/elyra/tree/main/etc/docker for how they...

I was thinking we could perhaps start by publishing `elyra-slim` / `kf-notebook-slim` which would not include any of the extras that the current `elyra` / `kf-notebook` pull in.

For reference: For source code Elyra builds its possible to customize which images are system-owned images by modifying the content of https://github.com/elyra-ai/elyra/tree/master/etc/config/metadata/runtime-images

Another possible alternative: Perhaps we could introduce a configuration setting that, if defined, causes the metadata service to ignore [system-owned entries](https://github.com/elyra-ai/elyra/tree/master/etc/config/metadata/runtime-images). This way these entries would not be listed in...