Install Atlassian Jira with Docker: Quick Start, Persistent Volumes, and Deployment Checks

Running Jira in Docker is a fast way to stand up a lab, demo, or self-managed test instance. This updated guide keeps the original command, explains what it does, and adds safer patterns for persistence, repeatability, and operational checks.

Originally published on 2016-02-23; fully revised and updated.

The original one-line Jira container command

The original post used this command to start Jira and publish the web UI on port 8080:

docker run --detach --publish 8080:8080 cptactionhank/atlassian-jira:latest

After startup, open http://localhost:8080 (or http://[dockerhost]:8080) and complete the Jira setup wizard.

Jira-in-Docker workflow

flowchart TD
    A[Choose image and tag] --> B[Prepare persistent storage]
    B --> C[Run container with port mapping]
    C --> D[Open setup wizard on port 8080]
    D --> E[Configure Jira and admin account]
    E --> F[Validate restart and data persistence]
    F --> G[Add backup and upgrade process]

Quick-start options compared

Commands you can run now

Original command from the post

docker run --detach --publish 8080:8080 cptactionhank/atlassian-jira:latest

Run with a named volume for Jira home data

docker volume create jira_home

docker run --detach \
  --name jira \
  --publish 8080:8080 \
  --volume jira_home:/var/atlassian/jira \
  cptactionhank/atlassian-jira:latestCode language: JavaScript (javascript)

This keeps Jira home data in a Docker-managed volume so data can survive container recreation.

Docker Compose baseline

services:
  jira:
    image: cptactionhank/atlassian-jira:latest
    container_name: jira
    ports:
      - "8080:8080"
    volumes:
      - jira_home:/var/atlassian/jira
    restart: unless-stopped

volumes:
  jira_home:Code language: JavaScript (javascript)

docker compose up -d

Important paths from the original post

These paths were listed in the original article and are commonly used in Jira container images, but confirm against the exact image and tag you run.

Post-start validation checks

docker ps --filter name=jira
docker logs -f jira
curl -I http://localhost:8080

docker restart jira
docker ps --filter name=jiraCode language: JavaScript (javascript)

• If the HTTP endpoint responds, the web service is reachable.
• After restart, verify Jira can still access existing data and configuration.
• If startup is slow, keep watching container logs until the web UI is ready.

Reference and attribution

Original post permalink: https://www.devopsschool.com/blog/install-atlassian-jira-using-docker/

Original image/reference source: https://hub.docker.com/r/cptactionhank/atlassian-jira/

The original page also contained a broken YouTube gallery embed; related troubleshooting link preserved here: https://www.youtube.com/watch?v=ZCfrNvu6nMc

Best practices and common pitfalls

• Avoid unpinned tags for reproducible environments; use a specific image tag after validation.
• Persist Jira home data with a Docker volume or host mount before doing meaningful setup work.
• Validate image provenance and maintenance status, especially for community images.
• Plan backup and restore for Jira home data before upgrades or host changes.
• Treat this as a starting point; confirm current Atlassian guidance for production-grade deployments.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.