Skip to content

Run in Docker

Christian Hueller edited this page Jul 17, 2020 · 7 revisions

You can avoid installing Catapult dependencies (besides Docker) by using a prepackaged catapult docker image:

$> docker run -v /var/run/docker.sock:/var/run/docker.sock -ti --rm splatform/catapult:latest dind

This will give you after a bit of waiting time a full bootstrapped SCF cluster, without any requirement except Docker.

Fun fact, this is the same image that CIs using catapult use and run. The image gets automatically created and uploaded by a pipeline every time there is commits in master that change the Dockerfile.

Default user/pass: admin/password

From the docker image

You can build the catapult docker image locally:

$> make catapult-image

Or you can use the docker image already built to start a cluster:

$> docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -ti splatform/catapult:latest dind

To tear it down:

$> docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -ti splatform/catapult:latest force-clean

You can provide the same options as running it locally, but you have to pass the environment variables with -e prefixed. e.g. docker run -e CHART_URL=xxx -v /var/run/docker.sock:/var/run/docker.sock --rm -ti splatform/catapult:latest k8s scf

Automatic creation of image

This is done by a pipeline, that builds the image from master.

Pipeline code: https://github.com/SUSE/cloudfoundry/blob/master/ci/pipelines/catapult/pipeline.yml

Pipeline instance: https://concourse.suse.de/teams/main/pipelines/catapult

Clone this wiki locally