Install Agent as Docker Container

Prerequisites

To use steadybit with the SaaS platform you only need a docker installation on the host where the attacks will be executed. In a future release we will provide more installation options.

Oneliner

The agent container image is available in the steadybit Docker Registry. Please note that the container needs to run in a privileged mode, allowing it to discover and attack your Infratructure. And check before installation whether the platform is accessible via the corresponding ports (443 and 7878).

curl -sfL https://get.steadybit.io/agent.sh | sh -s -- -a <agent-key> -e <platform-url>

For your convenience you can use the setup page in the SaaS platform, where your agent key is already prepared in the command.

Manual setup

First login to the steadybit Docker Registry:

docker login -u=_ -p=<agent-key> docker.steadybit.io

Then run the steadybit Agent Container:

sudo docker run \
--detach \
--name steadybit-agent \
--volume /var/run:/var/run \
--privileged \
--net=host \
--pid=host \
--ipc=host \
--env="STEADYBIT_AGENT_KEY=<agent.key>" \
--env="STEADYBIT_AGENT_REGISTER_URL=<platform-url>" \
docker.steadybit.io/steadybit/agent

Static Agent

We also provide a static version of docker image docker.steadybit.io/steadybit/agent-static having which already includes all features and has the auto-updates disabled by default.

Non-privileged container

In case you need to run the container non-privileged you can add the individual capabilities:

--security-opt apparmor:unconfined \
sudo docker run \
--detach \
--name steadybit-agent \
--volume /var/run:/var/run \
--cap-add=NET_ADMIN \
--cap-add=SYS_BOOT \
--cap-add=SYS_TIME \
--cap-add=KILL \
--security-opt apparmor:unconfined \
--net=host \
--pid=host \
--ipc=host \
--env="STEADYBIT_AGENT_KEY=<agent-key>" \
--env="STEADYBIT_AGENT_REGISTER_URL=<platform-url>" \
docker.steadybit.io/steadybit/agent
Need Help? Get in touch with us© steadybit. All rights reserved.