Documentation: https://chrisproject.org/docs/run/podman
miniChRIS-podman provides YAML files which can be read by podman play kube to run ChRIS.
It is a no-fuss solution for running ChRIS locally for demoing or testing.
miniChRIS-podman is insecure and not be used in production. However, we aim for its code to be as simple as possible, so that it can be used as a learning resource and starting point for writing production-ready configurations of ChRIS.
miniChRIS-podman runs applications in "production mode" (where applicable) so it's not great for the purpose of hacking ChRIS backend services themselves. For that, consult the project source repositories instead, e.g. https://github.com/FNNDSC/ChRIS_ultron_backEnd
Image tags are pinned to stable versions, so miniChRIS might be out-of-date with development versions of ChRIS components. Please contact us if the images are out of date.
For other ways to run ChRIS, see https://chrisproject.org/docs/run
YAML files in podman/kube should be interoperable between Podman and Kubernetes.
Podman supports a subset of the Kubernetes manifest spec:
Pod, Deployment, PersistentVolumeClaim, ConfigMap
Ideally, to add pfcon to CUBE we should be using the pod name of pfcon
http://minichris-pfcon:5005/api/v1/but it won't work.
See FNNDSC/ChRIS_ultron_backEnd#505
There is an undocumented behavior of Podman where the host is visible to the container
via the name host.containers.internal, and we're able to talk to pfcon via the bound
host port.