Developer Guide > Developer Guide > Codebeamer Architecture > Cluster Architecture > Running a Codebeamer Cluster with Docker-Compose
Running a Codebeamer Cluster with Docker-Compose
All the software required to run a Codebeamer cluster is also available as public docker images. With these resources, it is easy to spin up an instance in an isolated, safe manner with minimal dependencies. As multiple containers are required to run for a cluster to operate, some coordination is needed. There are several tools available for container orchestration. In the provided example, a Docker Compose file is given. The script can be easily adapted for other tools as well.
* 
You have to build your own image with the docker image builder script to be able to use the example compose files below. The image builder script can be downloaded from the Building a Docker Image for Codebeamer 2.2 and Later Versions.
docker-compose.yaml
* 
This is an example configuration, not a production ready setup. Use this only to understand the clustering feature.
MySQL is no longer a supported database in Codebeamer.
Save the file with name docker-compose.yaml into a separate folder like work/docker/cb.
Following are sample docker-compose.yaml files for various load balancer and worker node configurations:
Dependencies
Docker
Docker-compose
Usage
Navigate to the docker-compose.yml file location (provided below).
Issue command: docker-compose up . Use docker-compose -d up to run in the background.
Once bootstrapped and started, Codebeamer cluster can be accessed in the browser (http://localhost:8080/)
Use the username bond with the password 007 to log in.
To stop the containers, either exit the docker-compose process if it is running in the foreground, or, issue docker-compose down from the location of the docker-compose.yml file.
The clustered Codebeamer application will be available on the port of the cb-load-balancer-1 container on your localhost.
The instances of the Codebeamer cluster are available on the ports defined in the docker-compose.yaml file. In the example above, they are 9080 and 9090.
You need to access these instances in the browser in order to set up the licenses for the two Codebeamer applications separately.
* 
In a production environment, the ports 8090 and 9090 of the Codebeamer instances should not be exposed.
Codebeamer
The cluster can be accessed through the loadbalancer. http://localhost:8080
Codebeamer instances:
Codebeamer instance 1: http://localhost:9090
Codebeamer instance 2: http://localhost:9080
How to Test Cache Network Configurations
More details about executing Cache Test can be found here: Executing the Cluster Cache Configuration Test
Was this helpful?