/docker-crowd

Docker Image Packaging for Atlassian Crowd

Primary LanguageJinjaApache License 2.0Apache-2.0

Docker Image Packaging for Atlassian Crowd

AlviStack

GitLab pipeline status GitHub tag GitHub license Docker Pulls

Crowd is where you manage users from multiple directories - Active Directory, LDAP, Crowd - via a single admin console, and control application permissions from the same place.

Learn more about Crowd: https://www.atlassian.com/software/crowd

Supported Tags and Respective Packer Template Links

Overview

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

Based on Official Ubuntu Docker Image with some minor hack:

  • Packaging by Packer Docker builder and Ansible provisioner in single layer
  • Handle ENTRYPOINT with catatonit

Quick Start

For the CROWD_HOME directory that is used to store the repository data (amongst other things) we recommend mounting a host directory as a data volume, or via a named volume if using a docker version >= 1.9.

Volume permission is NOT managed by entry scripts. To get started you can use a data volume, or named volumes.

Start Atlassian Crowd Server:

# Pull latest image
docker pull alvistack/crowd-5.2

# Run as detach
docker run \
    -itd \
    --name crowd \
    --publish 8095:8095 \
    --volume /var/atlassian/application-data/crowd:/var/atlassian/application-data/crowd \
    alvistack/crowd-5.2

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

Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate both the application server and the git processes. See Supported Platforms for further information.

Upgrade

To upgrade to a more recent version of Crowd Server 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 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 Server 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 (/var/atlassian/application-data/crowd in the example above).

Versioning

YYYYMMDD.Y.Z

Release tags could be find from GitHub Release of this repository. Thus using these tags will ensure you are running the most up to date stable version of this image.

YYYYMMDD.0.0

Version tags ended with .0.0 are rolling release rebuild by GitLab pipeline in weekly basis. Thus using these tags will ensure you are running the latest packages provided by the base image project.

License

Author Information