Sut Setup Containers

Operator onboards a distributed key-value store with three server nodes and a client. They describe the topology to Antithesis.

Express the full multi-container topology (all server nodes, dependencies, and the test/workload container) as a Docker Compose configuration so Antithesis can run the whole system inside the simulation. Every component the system needs at runtime must be a container in that compose set — nothing a…

The compose file references images by tag ':latest'. The operator wants stable, reproducible test runs.

Pin every SUT image by immutable digest (sha256), not a mutable tag, so each run tests a known build and a reproduction months later rebuilds the identical environment. Tag mutation silently changes what is under test and breaks the reproducibility guarantee that is the whole point of the platform.

The SUT assumes 32 GB RAM available on the host. Under simulation it OOMs and the operator blames Antithesis.

Declare the SUT's resource expectations in the container configuration and size the simulated environment accordingly; the simulation provides resources to the containers, it does not inherit the host's full capacity by assumption. Right-size memory/CPU per container so OOMs reflect real SUT behavi…