This page describes the tasks necessary to deploy Curiefense using Docker Compose. The tasks are described sequentially below:
During this process, you might find it helpful to read the descriptions (which include the purpose, secrets, and network/port details) of the services and their containers: Services and Container Images
Clone the repository, if you have not already done so:
git clone https://github.com/curiefense/curiefense.git
This documentation assumes it has been cloned to
A Docker Compose deployment can use TLS for communication with Curiefense's UI server and also for the protected service, but this is optional. (If you do not choose to set it up, HTTPS will be disabled.)
If you do not want Curiefense to use TLS, then skip this step and proceed to the next section. Otherwise, generate the certificate(s) and key(s) now.
To enable TLS for the protected site/application, go to
curiefense/deploy/compose/curiesecrets/curieproxy_ssl/and do the following:
site.crtand add the certificate.
site.keyand add the key.
To enable TLS for the nginx server that is used by
uiserver, go to
curiefense/deploy/compose/curiesecrets/uiserver_ssl/and do the following:
ui.crtand add the certificate.
ui.keyand add the key.
Docker Compose deployments can be configured in two ways:
- By setting values for variables in
- Or by setting OS environment variables (which will override any variables set in
These variables are described below.
Curiefense uses the storage defined here for synchronizing configuration changes between
confserverand the Curiefense sidecars.
By default, this points to the
$ grep CURIE_BUCKET_LINK .env
For multi-node deployments, or to use S3 for a single node, replace this value with the URL of an S3 bucket:
In that case, you will need to supply AWS credentials in
deploy/compose/curiesecrets/s3cfg, following this template:
access_key = AAAAAAAAAAAAAAAAAAAA
secret_key = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
The address of the destination service for which Curiefense acts as a reverse proxy. By default, this points to the
echocontainer, which simply echoes the HTTP requests it receives.
main(the latest stable image, automatically built from the
mainbranch). To run a version that matches the contents of your working directory, use the following command:
DOCKER_TAG="$(git describe --tag --long --dirty)-$(git rev-parse --short=12 HEAD:curiefense)"
Once the tasks above are completed, run these commands:
After deployment, the Echo service should be running and protected behind Curiefense. You can test the success of the deployment by querying it:
$ curl http://localhost:30081/
Request served by echo
HTTP/1.1 GET /
Also verify the following:
To stop all containers and remove any persistent data stored in volumes, run the following commands:
docker-compose rm -f && docker volume prune -f