kingsquare/atlassian-crowd repository overview

⁠Please use the official Crowd Docker image⁠

⁠This is just here as a gentle reminder ;)

⁠unOfficial Atlassian Crowd docker

This is a dockerized version of Atlassian Crowd⁠ that mimics their other dockerized versions of various applications. (Bamboo⁠, Jira⁠ etc)

Who knows, this might be the exact same way they might do it officially.

Crowd is a centralized identity management server. Learn more about Crowd⁠.

⁠Overview

This Docker container makes it easy to get an instance of Crowd up and running.

⁠Quick Start

For the CROWD_HOME directory that is used to store, amongst other things, the configuration data we recommend mounting a host directory as a data volume⁠, or using a named volume.

Volume permission is managed by entry scripts. To get started you can use a data volume, or named volumes. In this example we'll use named volumes.

$> docker volume create --name atlassianCrowdVolume

Start Atlassian Crowd:

$> docker run -v /data/atlassian/crowd:/var/atlassian/application-data/crowd --name="crowd" --init -d -p 8095:8095 kingsquare/atlassian-crowd

Note that this command can be replaced by named volumes as noted above.

Success. Crowd is now available on http://localhost:8095⁠*.

Note that the --init flag is required to properly reap zombie processes.

Make sure your container has the necessary resources allocated to it.

⁠Upgrade

To upgrade to a more recent version of Crowd you can simply stop the crowd container and start a new one based on a more recent image:

$> docker stop crowd
$> docker rm crowd
$> docker pull kingsquare/atlassian-crowd:<desired_version>
$> docker run ... (See above)

As your data is stored in the data volume directory on the host it will still be available after the upgrade.

Note: Please make sure that you don't accidentally remove the crowd container and its volumes using the -v option.

⁠Backup

For evaluations you can use the built-in database that will store its files in the Crowd home directory. In that case it is sufficient to create a backup archive of the directory on the host that is used as a volume (/data/atlassian/crowd in the example above).

⁠Production load

If using this image for non-evaluations (i.e. Production usage) we strongly advise to use the volume for Crowd.

⁠MySQL driver

When using Crowd with MySQL⁠ as a backing datastore, you will have to download the [driver (JAR)][https://dev.mysql.com/downloads/connector/j/⁠] and mount / copy it into the container (using ${CROWD_INSTALL}/apache-tomcat/lib/ as the destination) when starting / building a new image.

⁠Versioning

The latest tag matches the most recent version of this repository. Thus using kingsquare/atlassian-crowd:latest or kingsquare/atlassian-crowd will ensure you are running the most up to date version of this image.

However, we ** strongly recommend ** that for non-eval workloads you select a specific version in order to prevent breaking changes from impacting your setup. You can use a specific minor version of Crowd by using a version number tag: kingsquare/atlassian-crowd:3.7. This will install the latest 3.7.x stable version that is available.

⁠Support

As this is the non official image, please use this issue tracker or report your Crowd specific issue to Atlassian Support⁠.

⁠Credits

This readme, the Dockerfile and entrypoint were heavily inspired by the official Bamboo-docker project and thus Atlassian takes most (if not all) of the credits.