本站支持搜索的镜像仓库:Docker Hub、gcr.io、ghcr.io、quay.io、k8s.gcr.io、registry.gcr.io、elastic.co、mcr.microsoft.com
Current litmuschaos-server Docker Image from Canonical, based on Ubuntu. Receives security updates and rolls to newer litmuschaos-server or Ubuntu release. This repository is free to use and exempted from per-user rate limits.
Litmuschaos is a chaos testing platform for kubernetes applications. It allows you to define, run and monitor 'chaos experiments' that simulate infrastructure failures to verify the stability of your cloud deployments. Read more on the official documentation This rock deploys the backend component, also known as the 'graphql server'. Please note that this repository is now holding a rock, not a Dockerfile-based image. As such the entrypoint is now Pebble. Read more on the Rockcraft docs.
!LTS Up to 5 years of free security maintenance on LTS channels.
!ESM Up to 10 years of customer security maintenance from Canonical's restricted repositories.
| Channel Tags | Supported until | Currently | Architectures |
|---|---|---|---|
3.21-24.04_edge | - | litmuschaos-server 3.21 on Ubuntu 24.04 LTS | amd64 |
3.20-24.04_edge | - | litmuschaos-server 3.20 on Ubuntu 24.04 LTS | amd64 |
3.19-24.04_edge | - | litmuschaos-server 3.19 on Ubuntu 24.04 LTS | amd64 |
track_risk |
Channel Tags shows the most stable channel for that track ordered stable, candidate, beta, edge. More risky channels are always implicitly available. So if beta is listed, you can also pull edge. If candidate is listed, you can pull beta and edge. When stable is listed, all four are available. Images are guaranteed to progress through the sequence edge, beta, candidate before stable.
If your usage includes commercial redistribution, or requires ESM or unavailable channels/versions, please get in touch with the Canonical team (or using ***).
Launch this image locally:
docker run -d --name litmuschaos-server-container -e TZ=UTC -p 3000:3000 ubuntu/litmuschaos-server:3.21-24.04_edge
Access the backend server instance at http://localhost:3000.
| Parameter | Description |
|---|---|
-e VERSION=<version> | ID of the running version. |
-e INFRA_DEPLOYMENTS='["app=chaos-exporter"]' | Deployment names for the infra components. |
-e SUBSCRIBER_IMAGE="litmuschaos/litmusportal-subscriber:ci" | Image the chaoscenter will use to deploy the subscriber service. |
-e EVENT_TRACKER_IMAGE="litmuschaos/litmusportal-event-tracker:ci" | Image the chaoscenter will use to deploy the event-tracker service. |
-e ARGO_WORKFLOW_CONTROLLER_IMAGE="litmuschaos/workflow-controller:v3.3.1" | Image the chaoscenter will use to deploy the argo-workflow-controller service. |
-e ARGO_WORKFLOW_EXECUTOR_IMAGE="litmuschaos/argoexec:v3.3.1" | Image the chaoscenter will use to deploy the argo-workflow-executor service. |
-e LITMUS_CHAOS_OPERATOR_IMAGE="litmuschaos/chaos-operator:ci" | Image the chaoscenter will use to deploy the chaos-operator service. |
-e LITMUS_CHAOS_RUNNER_IMAGE="litmuschaos/chaos-runner:ci" | Image the chaoscenter will use to deploy the chaos-runner service. |
-e LITMUS_CHAOS_EXPORTER_IMAGE="litmuschaos/chaos-exporter:ci" | Image the chaoscenter will use to deploy the chaos-exporter service. |
-e CONTAINER_RUNTIME_EXECUTOR="k8sapi" | Runtime executor. |
-e WORKFLOW_HELPER_IMAGE_VERSION="ci" | Image version tag for the workflow helper. |
-e INFRA_COMPATIBLE_VERSIONS="ci" | Image version tag for the infra workloads. |
-e DEFAULT_HUB_BRANCH_NAME="master" | Default branch name for gitops repos. |
-e ADMIN_USERNAME=<user> | Web UI admin username. |
-e ADMIN_PASSWORD=<password> | Web UI admin password. |
-e DB_SERVER=<db_address> | Database server address. |
-e DB_USER=<db_user> | Database username. |
-e DB_PASSWORD=<db_password> | Database password. |
-e REST_PORT=3000 | REST API auth server port. |
-e GRPC_PORT=3030 | gRPC auth server port. |
-p 3000:3000 | Access the backend server at http://localhost:3000. |
To debug the container:
docker logs -f litmuschaos-server-container
To get an interactive shell:
docker exec -it litmuschaos-server-container /bin/bash
To run the server:
# litmuschaos-server needs a MongoDB database to work docker run -d --name mongodb -e MONGO_INITDB_ROOT_USERNAME=root -e MONGO_INITDB_ROOT_PASSWORD=password -p 27017:27017 mongo:7 # don't use `--network host` in production docker run -d --network host -p 3000:3000 --name litmuschaos-server-container \n -e DB_USER=root \n -e VERSION=ci \n -e DB_PASSWORD=password \n -e REST_PORT=3000 \n -e GRPC_PORT=3030 \n -e DB_SERVER=mongodb://localhost:27017 \n -e ADMIN_USERNAME=admin \n -e ADMIN_PASSWORD=password \n -e INFRA_DEPLOYMENTS='["app=chaos-exporter"]' \n -e SUBSCRIBER_IMAGE="litmuschaos/litmusportal-subscriber:ci" \n -e EVENT_TRACKER_IMAGE="litmuschaos/litmusportal-event-tracker:ci" \n -e ARGO_WORKFLOW_CONTROLLER_IMAGE="litmuschaos/workflow-controller:v3.3.1" \n -e ARGO_WORKFLOW_EXECUTOR_IMAGE="litmuschaos/argoexec:v3.3.1" \n -e LITMUS_CHAOS_OPERATOR_IMAGE="litmuschaos/chaos-operator:ci" \n -e LITMUS_CHAOS_RUNNER_IMAGE="litmuschaos/chaos-runner:ci" \n -e LITMUS_CHAOS_EXPORTER_IMAGE="litmuschaos/chaos-exporter:ci" \n -e CONTAINER_RUNTIME_EXECUTOR="k8sapi" \n -e WORKFLOW_HELPER_IMAGE_VERSION="ci" \n -e INFRA_COMPATIBLE_VERSIONS="ci" \n -e DEFAULT_HUB_BRANCH_NAME="master" \n ubuntu/litmuschaos-server:3.19-24.04_edge
Note that at this point the workload still won't be operational, as it requires the litmuschaos-auth and litmuschaos-frontend components to function.
Cleanup:
docker rm -f mongodb docker rm -f litmuschaos-server-container
If you find a bug in our image or want to request a specific feature, please file a bug here:
[***]
Please title the bug "litmuschaos-server: <issue summary>". Make sure to include the digest of the image you are using, from:
docker images --no-trunc --quiet ubuntu/litmuschaos-server:<tag>
These channels (tags) are not updated anymore. Please upgrade to newer channels, or reach out if you can't upgrade.
| Track | Version | EOL | Upgrade Path |
|---|---|---|---|
track |

免费版仅支持 Docker Hub 加速,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
免费版仅支持 docker.io;专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录方式配置轩辕镜像加速服务,包含7个详细步骤
在 Linux 系统上配置轩辕镜像源,支持主流发行版
在 Docker Desktop 中配置轩辕镜像加速,适用于桌面系统
在 Docker Compose 中使用轩辕镜像加速,支持容器编排
在 k8s 中配置 containerd 使用轩辕镜像加速
在宝塔面板中配置轩辕镜像加速,提升服务器管理效率
在 Synology 群晖NAS系统中配置轩辕镜像加速
在飞牛fnOS系统中配置轩辕镜像加速
在极空间NAS中配置轩辕镜像加速
在爱快ikuai系统中配置轩辕镜像加速
在绿联NAS系统中配置轩辕镜像加速
在威联通NAS系统中配置轩辕镜像加速
在 Podman 中配置轩辕镜像加速,支持多系统
配置轩辕镜像加速9大主流镜像仓库,包含详细配置步骤
无需登录即可使用轩辕镜像加速服务,更加便捷高效
需要其他帮助?请查看我们的 常见问题 或 官方QQ群: 13763429