Skip to content
Switch branches/tags
Go to file
Latest commit ba55299 Sep 30, 2023 History
2 contributors

Users who have contributed to this file

@skoranda @satkinson

Evaluating COmanage Registry using Docker

Follow these steps to build and run a simple deployment of COmanage Registry suitable for evaluation purposes.

  • Install Docker. These instructions require version 17.05 or higher.

  • Install Docker Compose. These instructions require version 1.13.0 or higher.

  • Clone this repository:

git clone
cd comanage-registry-docker
  • Define the shell variable COMANAGE_REGISTRY_VERSION to be the version of COmanage Registry you want to deploy. See the COmanage Registry Release History wiki page for the list of releases. We recommend using the latest release.

Here is an example (but please check the wiki page for the latest release number):

  • Build the base COmanage Registry image:
pushd comanage-registry-base
docker build \
    -t comanage-registry-base:${COMANAGE_REGISTRY_VERSION}-1 .
  • Build an image for COmanage Registry that uses basic authentication:
pushd comanage-registry-basic-auth
docker build \
    -t comanage-registry:${COMANAGE_REGISTRY_VERSION}-basic-auth .
  • Build a local image of PostgreSQL for COmanage Registry:
pushd comanage-registry-postgres
docker build -t comanage-registry-postgres .
  • Create a docker-compose.yml file:
version: '3.1'


        image: comanage-registry-postgres

        image: "comanage-registry:${COMANAGE_REGISTRY_VERSION}-basic-auth"
            - "80:80"
            - "443:443"
  • Start the services:
docker-compose up -d
  • Browse to port 443 on the host, for example https://localhost/. You will have to click through the warning from your browser about the self-signed certificate used for HTTPS.

  • Click Login and when prompted enter registry.admin as the username and password for the password.

  • Visit the COmanage wiki to learn how to create your first collaborative organization (CO) and begin using the platform.

  • To stop the services:

docker-compose stop
  • To remove the containers and networks:
docker-compose down

Important Notes

The instructions above are not suitable for a production deployment for two reasons:

  1. The deployed services use default and easily guessed passwords.
  2. No data is persisted. When the containers are destroyed so is your data.

Next Steps

To evolve your COmanage Registry deployment examine the documentation in the docs directory.