Creating your own devfile registry


You need a Kubernetes or OpenShift cluster (eg., minikube or minishift), into which you have installed Che. Follow the steps in this document to deploy Che.

Steps below can then be done to deploy a custom devfile registry to your cluster, and use it with Che.


git clone
cd che-devfile-registry
  • Make changes in the devfiles/ folder to add new or remove existing devfile folders from the registry.
  • Build the image.

This example uses a personal quay repository and an arbitrary tag ubi8-2, but you can use another image registry and path as needed.

docker build . -f Dockerfile --no-cache \
  • Push it to quay (or your image registry of choice)
docker push

Verify the image and tag you pushed are published, eg.,
Verify the Repository Visibility is public, eg.,

  • Remove any existing che-devfile-registry deployments.
oc delete dc che-devfile-registry; \
oc delete svc che-devfile-registry; \
oc delete route che-devfile-registry; \
sleep 5s
  • Deploy the new che-devfile-registry.
oc new-app -f deploy/openshift/che-devfile-registry.yaml \
  -p PULL_POLICY="Always" \
  -p IMAGE="" \
  -p IMAGE_TAG="ubi8-2"; \
sleep 5s

Published on Java Code Geeks with permission by Nick Boldt , partner at our JCG program. See the original article here: Creating your own devfile registry

Opinions expressed by Java Code Geeks contributors are their own.

Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments
Back to top button