mirror of
https://github.com/EpicMorg/docker-scripts.git
synced 2025-06-12 05:52:06 +03:00
readme moved to jira catalog
This commit is contained in:
parent
cdafd18f9f
commit
a55d6dee07
linux/atlassian/jira
5
6
7
7.0.0
7.0.10
7.0.11
7.0.2
7.0.4
7.0.5
7.1.0
7.1.1
7.1.10
7.1.2
7.1.4
7.1.6
7.1.7
7.1.8
7.1.9
7.10.0
7.10.1
7.10.2
7.11.0
7.11.1
7.11.2
7.12.0
7.12.1
7.12.3
7.13.0
7.13.1
7.13.11
7.13.12
7.13.13
7.13.2
7.13.3
7.13.4
7.13.5
7.13.6
7.13.8
7.13.9
7.2.0
7.2.1
7.2.10
7.2.11
7.2.12
7.2.13
7.2.14
7.2.15
7.2.2
7.2.3
7.2.4
7.2.6
7.2.7
7.2.8
7.2.9
7.3.0
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8
7.3.9
7.4.0
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
7.5.0
7.5.1
7.5.2
7.5.3
7.5.4
7.6.0
7.6.1
7.6.10
7.6.11
7.6.12
7.6.13
7.6.14
7.6.15
7.6.16
7.6.17
7.6.2
7.6.3
7.6.4
7.6.6
7.6.7
7.6.8
7.6.9
7.7.0
7.7.1
7.7.2
7.7.4
7.8.0
7.8.1
@ -1,8 +0,0 @@
|
||||
# Atlassian Enterprise releases
|
||||
## Build info
|
||||
|
||||
All presented images avalible on our repo in docker hub.
|
||||
|
||||
-------
|
||||
|
||||
*Some old versions of Jira may fail health check with [AdoptOpenJDK](https://github.com/AdoptOpenJDK) (open source, prebuilt OpenJDK binaries). But it will be works.*
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,8 +0,0 @@
|
||||
# Atlassian Enterprise releases
|
||||
## Build info
|
||||
|
||||
All presented images avalible on our repo in docker hub.
|
||||
|
||||
-------
|
||||
|
||||
*Some old versions of Jira may fail health check with [AdoptOpenJDK](https://github.com/AdoptOpenJDK) (open source, prebuilt OpenJDK binaries). But it will be works.*
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
@ -1,151 +0,0 @@
|
||||
|
||||
|
||||
JIRA Software is a software development tool used by agile teams.
|
||||
|
||||
Learn more about JIRA Software: <https://www.atlassian.com/software/jira>
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of JIRA Software up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `JIRA_HOME` directory that is used to store application data (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name jiraVolume
|
||||
$> docker run -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
|
||||
**Success**. JIRA is now available on [http://localhost:8080](http://localhost:8080)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it. We recommend 2GiB of memory allocated to accommodate the application server. See [System Requirements](https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8080` instead._
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override JIRA's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 384m)
|
||||
|
||||
The minimum heap size of the JVM
|
||||
|
||||
* `JVM_MAXIMUM_MEMORY` (default: 768m)
|
||||
|
||||
The maximum heap size of the JVM
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If JIRA is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html), then you need to specify extra options to make JIRA aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which JIRA is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA_CONNECTOR_SCHEME is 'https'.
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to JIRA, such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for JIRA
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/jira/cacerts -v jiraVolume:/var/atlassian/application-data/jira --name="jira" -d -p 8080:8080 epicmorg/jira
|
||||
|
||||
## Data Center configuration
|
||||
|
||||
This docker image can be run as part of a [Data Center](https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html) cluster. You can specify the following properties to start Jira as a Data Center node, instead of manually configuring a cluster.properties file, See [Installing Jira Data Center](https://confluence.atlassian.com/adminjiraserver071/installing-jira-data-center-802592197.html) for more information on each property and its possible configuration.
|
||||
|
||||
* `CLUSTERED` (default: false)
|
||||
|
||||
Set 'true' to enable clustering configuration to be used. This will create a **cluster.properties** file inside the container's `$JIRA_HOME` directory.
|
||||
|
||||
* `JIRA_NODE_ID` (default: jira_node_<container-id>)
|
||||
|
||||
The unique ID for the node. By default, this will include the first eight characters of the Docker container ID, but can be overridden with a custom value.
|
||||
|
||||
* `JIRA_SHARED_HOME` (default: $JIRA_HOME/shared)
|
||||
|
||||
The location of the shared home directory for all Jira nodes.
|
||||
|
||||
* `EHCACHE_PEER_DISCOVERY` (default: default)
|
||||
|
||||
Describes how nodes find each other.
|
||||
|
||||
* `EHCACHE_LISTENER_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname of the current node for cache communication. Jira Data Center will resolve this this internally if the parameter isn't set.
|
||||
|
||||
* `EHCACHE_LISTENER_PORT` (default: 40001)
|
||||
|
||||
The port the node is going to be listening to.
|
||||
|
||||
* `EHCACHE_LISTENER_SOCKETTIMEOUTMILLIS` (default: 2000)
|
||||
|
||||
The default timeout for the Ehcache listener.
|
||||
|
||||
* `EHCACHE_MULTICAST_ADDRESS` (default: NONE)
|
||||
|
||||
A valid multicast group address. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_PORT` (default: NONE)
|
||||
|
||||
The dedicated port for the multicast heartbeat traffic.Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_TIMETOLIVE` (default: NONE)
|
||||
|
||||
A value between 0 and 255 which determines how far the packets will propagate. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
* `EHCACHE_MULTICAST_HOSTNAME` (default: NONE)
|
||||
|
||||
The hostname or IP of the interface to be used for sending and receiving multicast packets. Required when EHCACHE_PEER_DISCOVERY is set to 'automatic' insted of 'default'.
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of JIRA you can simply stop the `jira` container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop jira
|
||||
$> docker rm jira
|
||||
$> 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 `jira` 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 JIRA home directory. In that case it is sufficient to create a backup archive of the docker volume.
|
||||
|
||||
If you're using an external database, you can configure JIRA to make a backup automatically each night. This will back up the current state, including the database to the `jiraVolume` docker volume, which can then be archived. Alternatively you can backup the database separately, and continue to create a backup archive of the docker volume to back up the JIRA Home directory.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html](https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian JIRA Software. Thus `epicmorg/jira:latest` will use the newest version of JIRA available.
|
||||
|
||||
## Versions available
|
||||
|
||||
* `epicmorg/jira:latest`
|
||||
* `epicmorg/jira:7.10.0`
|
||||
|
||||
# Support
|
||||
|
||||
This Docker container is unsupported and is intended for illustration purposes only.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user