Public | Automated Build

Last pushed: 10 months ago
Short Description
Simple container for Atlassian JIRA
Full Description


Simple Docker container for Atlassian JIRA based on phusions ubuntu base-image (include mysql jar connector)

Build Docker JIRA instance

In order to connect with ssh, you should add your ssh keys in a config/ directory. Then you can build it.

sudo docker build -t="houseofagile/docker-jira" .

Run your JIRA docker instance

sudo docker run -d --name docker-jira -P houseofagile/docker-jira

It could be nice to link jira with your mysql instance and to mount your jira-home as a volume

hoa_instance=jira-prod-staropramen && docker run -d -h $hoa_instance --name $hoa_instance --link staropramen-mysql:heypet-mysql -v /srv/volumes/jira-prod:/opt/jira-home houseofagile/docker-jira

Add a vhost on your docker root host

The JIRA docker instance should run smoothly in the background, thanks to phusion baseimage, you should be able to connect to it through ssh. depending on your ssh settings, you either connect with the insecure ssh key or with your personal key (which we recommand).

Find the IP of your docker jira container

Use either docker ps or some useful script

user@someserver:~$ do_get_ip_address 
63d0c34992e4    houseofagile/docker-jira:latest
de06f34dcf38    beaudev/mysql:latest
347ad346baa3    beaudev/docker-nginx:latest
f3d8d346264c    beaudev/scripter:latest
e27873454be2    mypostgre/postgresql:latest
cf99a3496f47    docker-wordpress-nginx-fr:latest

Access your JIRA install

Simple nginx vhost proxy

Once again, thanks to some useful nginx proxy creation script, you can add a vhost to your container easily.

user@someserver:~$ do_nginx_proxy_vhost
Updating proxy for host:
Restarting nginx: nginx.

Use it with jwilder nginx proxy


docker run -e VIRTUAL_HOST="$DOMAIN_NAMES" -e LETSENCRYPT_HOST="$DOMAIN_NAMES" -e LETSENCRYPT_EMAIL="" -h $PROJECT_NAME   -v /srv/volumes/jira-prod:/opt/jira-home --name $PROJECT_NAME -d -P houseofagile/docker-jira

Use it with traefik

Find the private IP of your docker instance (for example here) and configure your toml file.

# example configuration
url = ""


backend = "jira"
passHostHeader = true
rule = "Host:,"

Upgrading to latest version of JIRA

Recommended way could be to deploy it into another subdomain, work on the migration and switch it to your production version. Stopping production version first is recommended so that your user do not update the db.

Small summary guidelines:

  1. backup system with your current production server and stop current production server
  2. build new version and configure access to a new temp domain
  3. run your new docker instance without jira-home volume and do a fresh install with your new temp domain
  4. stop your new docker instance and mount it with your jira-home directory mounted as a volume
  5. start new docker instance and restore system with your backup
  6. your new jira server should be now running the new version of JIRA
  7. stop your new jira server, switch jira site url from your temp domain to your prod domain and restart your new jira server.


Enable SSL for JIRA

Using jira in a docker behind a proxy with ssl support could be painful, in a classic traefik environment, your https traffic is also sent to your backend, but then JIRA could be lost.
First switch your jira site scheme in the jira system to https and then edit /opt/jira/conf/server.xml.

<Service name="Catalina">

    <Connector port="8080"


               <!-- Add those 3 lines with your jira domain name -->
               <!-- end -->

Docker Pull Command
Source Repository