This repository provides a Dockerfile to build a containerized version of Siege, a powerful HTTP load testing and benchmarking tool.
Built upon a debian slim image, autobuilt and pushed once a week.
- Getting Started
- Build the Image Locally
- Specify a Siege Version
- Using the Docker Image
- Refer to Siege Documentation
To use this Docker image, ensure you have Docker installed on your system. The image can be used directly from a container registry (e.g., DockerHub) or built locally using the provided Dockerfile.
If you want to build the Docker image locally, clone this repository and use the following steps:
-
Clone the repository:
git clone https://github.com/stone/siege-docker.git cd siege-docker
-
Build the image using Docker:
docker build -t siege:latest .
-
(Optional) Specify a Siege version during the build:
docker build --build-arg SIEGE_VERSION=<desired_version> -t siege:<desired_version> .
Replace
<desired_version>
with the specific version of Siege you want to use (e.g.,4.1.7
).You find releases here: https://download.joedog.org/siege/
By default, the image is built with the version specified in the Dockerfile. To use a specific version:
-
During build, pass the desired version using the
--build-arg
option:docker build --build-arg SIEGE_VERSION=4.1.7 -t siege:4.1.7 .
-
If pulling from a dockerhub remote registry, check the available tags to see specific versions.
Run the Siege container using the following command:
docker run --rm ttyse/siege:latest --help
To test a URL, pass it as an argument to the container:
docker run --rm ttyse/siege:latest https://example.com
You can also bind local configuration files or volumes if needed:
docker run --rm -v $(pwd)/config:/root/.siege ttyse/siege:latest https://example.url
For more advanced usage and options, refer to the Siege Manual.
For detailed information on how to configure and use Siege, refer to its official documentation: https://www.joedog.org/siege-manual/.