ubuntu/litmuschaos-runner

ubuntu/litmuschaos-runner is a rock for litmuschaos-runner maintained by Canonical.

Litmus Chaos Runner is a Kubernetes controller that executes chaos experiments in target pods as part of the LitmusChaos platform.

[Learn more about litmuschaos-runner]

Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels.

Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble]

Inspect

To view the Pebble services and checks defined in this rock:

sh
docker run --rm ubuntu/litmuschaos-runner:3.26-24.04_edge plan

sh
docker inspect --format='{{.Config.Entrypoint}} {{.Config.Cmd}}' ubuntu/litmuschaos-runner:3.26-24.04_edge

Run

To run this rock, use any of the usual container runtimes, for example, docker:

sh
docker run --name litmuschaos-runner-container \
    ubuntu/litmuschaos-runner:3.26-24.04_edge

The Litmus Chaos Runner is intended to be deployed as a Kubernetes controller. Refer to the official documentation for deployment instructions.

Get logs

To view the logs of the running container, run:

sh
docker exec litmuschaos-runner-container pebble logs

Or, for a specific service:

sh
docker exec litmuschaos-runner-container pebble logs <service>

sh
docker logs litmuschaos-runner-container

Monitor health checks

Rocks may have predefined health checks that you can list by running:

sh
docker exec litmuschaos-runner-container pebble checks

The overall health of your container can be inspected via:

sh
docker exec litmuschaos-runner-container pebble health

\https://github.com/canonical/litmus-rocks/issues%5C]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy.