Pro's and Con's of Jira service desk if..?

[KRC]

What are the pro's and con's when jira service desk  data center is deployed in a docker  container setup rather than in a regular fashion?

[Marty · Accepted solution]

Hi,

I am not on the Jira Service Desk Team, but I will try to help.

I'd recommend you read this overview of Jira Data Center (including architecture) https://confluence.atlassian.com/enterprise/jira-data-center-472219731.html

The install guide is here: https://confluence.atlassian.com/adminjiraserver073/installing-jira-data-center-861253059.html

As you can see from the architecture, you need a load balancer, some jira nodes and shared file system and database.

Each JIRA node must run on its own machine (physical or virtual), with a separate machine for the shared services. The shared services machine must be accessible by each node.

So if you were trying to run Jira Data Center in Docker you'd need one container per node plus one for the load balancer plus at least one node for the shares services.

In general running any application within Docker has pros and cons.  You'll need to configure enough resources (CPU, memory, disk) for the Docker container to allow the app to run with performance.  You'd also need to configure network and disk access to enable the nodes to talk to the shared services, load balancer, etc. 

I don't think I would recommend running your production instance inside Docker.  

For non-production environments like for development or test you might be ok.  There are no official Docker images but I did find these:

https://github.com/codeclou/docker-atlassian-jira-data-center

https://github.com/fllaca/jira-datacenter-docker

I hope that helps!

[KRC]

Thank you for providing your insights and for sharing your knowledge.