Skip to main content
Version: 2.6.3

Configure the Development Environment

This document describes how to configure a local development environment for Chaos Mesh.

Most components of Chaos Mesh are only designed for Linux, so we suggest that you also configure your development environment to run on Linux. For example, use a virtual machine or WSL 2 and use VSCode Remote as your editor.

This document assumes that you are using Linux, without the limitations of specific Linux distributions. If you insist on using Windows/MacOS, you may need some tricks to make it work for you (For example, some make targets may fail depending on the environment).

Configuration Requirements

Before configuring, it is recommended that you install the development tools listed below, most of them may already be installed in your environment:


Compiling Chaos Mesh

After installing, follow the steps below to compile Chaos Mesh.

  1. Clone the Chaos Mesh repository to your local server:

    git clone
    cd chaos-mesh
  2. Make sure that Docker is installed and running.


    Chaos Mesh relies on Docker to build container images, this is for consistency with the production environment.

  3. Compile Chaos Mesh:

    UI=1 make image

    UI=1 means that we will compile the user interface of Chaos Dashboard, if you don't need it, you can omit this env.


    If you want to specify the tag of the image, you can use UI=1 make IMAGE_TAG=dev image.

    After compiling, you should get the following container images:


Run Chaos Mesh in local minkube Kubernetes cluster

Now you can run Chaos Mesh in a local Kubernetes cluster after compiling.

  1. Start a local Kubernetes cluster with minkube:

    minikube start
  2. Load container images into minikube:

    minikube image load
    minikube image load
    minikube image load
  3. Install Chaos Mesh by Helm:

    helm upgrade --install chaos-mesh-debug ./helm/chaos-mesh --namespace=chaos-mesh-debug --create-namespace

minikube image load would cost lots of time, so here is a trick to avoid load images again and again during development. Using docker from minikube node instead of host's docker:

minikube start --mount --mount-string "$(pwd):$(pwd)"
eval $(minikube -p minikube docker-env)
UI=1 make image

Debug Chaos Mesh in local environment

We could use delve with remote debugging to debug the Chaos Mesh in local environment.

  1. Compile Chaos Mesh with DEBUGGER=1:

    UI=1 DEBUGGER=1 make image
  2. Load container images into minikube:

    minikube image load
    minikube image load
    minikube image load
  3. Install Chaos Mesh and enable Remote Debugging:

    helm upgrade --install chaos-mesh-debug ./helm/chaos-mesh --namespace=chaos-mesh-debug --create-namespace --set chaosDlv.enable=true --set controllerManager.leaderElection.enabled=false

    To ensure high availability, Chaos Mesh turns on leader-election feature by default and will create 3 replicas for chaos-controller-manager. We will use controllerManager.leaderElection.enabled=false to ensure that Chaos Mesh only creates 1 instance of chaos-controller-manager for easier debugging.

    For more details, see Install Chaos Mesh in different environments.

  4. Setup Port-Forwarding and Configure IDE To Connect the Remote Debugger:

    We could use kubectl port-forward to forward the delve debugging server to a local port.

    For example, if we want to debug chaos-controller-manger, we could execute the following command:

    kubectl -n chaos-mesh-debug port-forward chaos-controller-manager-766dc8488d-7n5bq 58000:8000

    Then we could access the remote delve debugger server with


    We always use 8000 in the pod for serving the delve debug server, that's a convention. You could find that in helm templates files.

    Then we could configure our favorite IDE to connect to the remote debugger, below are some examples:

For more detailed information, see for container image chaos-dlv.

What's Next

After finishing the above preparation, you can try to Add a New Chaos Experiment Type.


Run make fail with error obtaining VCS status: exit status 128 in MacOS

The reason is related to It's recommended you to read it first.

Chaos Mesh will start the container (dev-env or build-env) with the current user (when you call make). You can find the appropriate --user flag in So when Git is looking for a top-level .git directory, it will stop if its directory traversal changes ownership from the current user.

A temporary solution for now is to comment out the line of --user.