Atlassian Confluence for Docker
You may also be interestd in the following projects:
- Dockerized Atlassian Crowd - centralized identity management
- Dockerized Atlassian JIRA - project tracking for software teams
This revision of docker-atlassian-confluence will install:
This application is ready to launch on a Docker host:
prompt> docker run -d -p 8080:8080 -p 8443:8443 markeissler/atlassian-confluence:latest
As configured, data on the following volumes will be created to persist data between container starts:
Data Persistence over NFS
It may be desirable to configure data persistence over NFS, in which case NFS volumes are mounted at the locations described in the Data Persistence section above. NFS support requires that the underlying Docker host supports NFS; if deploying to a Docker swarm a potential boot2docker.iso candidate that supports NFS is the [boot2docker-nfs.iso (https://github.com/markeissler/boot2docker-nfs).
Certain JIRA directories are moved out of the application configuration directory and into an ephemeral runtime storage area to prevent data corruption startup failures. Specfically, cache directories are moved so that clean re-starts are possible; often, when an instance dies Tomcat will not be shutdown cleanly and data corruption is likely to occur with regard to the felix plugin cache).
|/var/atlassian/confluence_runtime||runtime storage for caches and indexes|
You can enable SSL by simply copying a PKCS12 format certificate (
certificate.p12) into the
CONF_HOME directory (
/var/atlassian/confluence) and then restarting the container. The PKCS12 file format has been selected to make it easier to generate certificates using
openssl command that will create a PKCS12 file from a private key (
server_key.pem) and public certficate (
prompt> openssl pkcs12 -export -in server_cert.pem \ -inkey server_key.pem -out certificate.p12 \ -passout pass:changeit -name "confluence"
On container startup, the PCKS12 format certificate.p12 file will be converted and stored in the system JKS keystore.
Docker Swarm Support
While docker-atlassian-confluence does not support multi-node clustering it does support deployment to a cluster with a failover configuration (where only a single Confluence instance is active at any time).
This configuration requires that Data Persistence over NFS has been configured to share Confluence configuration information among replicated instances.
Redeployment Index Regeneration
Indexes are stored in ephemeral storage; consequently, when redeploying the application on top of existing persistent storage (i.e. Data Persistence over NFS) it will be necessary to manually trigger a rebuild of all indexes. Log in as a user with administrative permissions, then navigate to:
Cog > General Configuration > Administration > Content Indexing
Click on the <kbd>rebuild</kbd> button.
For general troubleshooting information check the Troubleshoot document.
Upstream Release Notes
Release notes for all versions of Confluence can be viewed online:
docker-atlassian-confluence is the work of Mark Eissler.
docker-atlassian-confluence was inspired by the work of Martin Aksel Jensen, specifically his ongoing efforts to provide up-to-date dockerized versions of other popular [Atlassian (https://www.atlassian.com/)
docker-atlassian-confluence is licensed under the MIT open source license.
Without open source, there would be no Internet as we know it today.