JIRA in Docker container fails to start

[steve_pole]

error message:

```

01-Oct-2019 19:11:25.110 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: [/opt/atlassian/jira/conf/Catalina/localhost]

```

[JesseBorden]

Catalina.start should print something out to say “Confluence is Started” or something like that. I believe Jira says something like “Jira is ready to serve”. Something like that would be good for Confluence as well. The last log of Catalina.start isn’t very helpful to know that it is running.

[Tinker Fadoua]

@steve_pole 

• What's the OS?
• Where did you download your JIRA Software image from?

Best

Fadoua

[steve_pole]

Well, it‘s the official Atlassian Docker container, so OS is some Linux, presumably some Ubuntu.

I didn‘t download any software, I just built a container image.

[Tinker Fadoua]

Aha, because I installed Docker on MacOS, then ran the container. Jira is up and running without any issues.

[steve_pole]

yeah, same here - everything worked fine on the MacBook, but failed on the Linux server.

The problem is / was related to JIRA not being able to create the `"${JIRA_INSTALL}/conf/Catalina"` folder when starting up due to that folder having `root` permissions and JIRA running as `jira` at that stage.

Seems like the new version of the Dockerfile (released 21 hours ago) fixed that.

[steve_pole]

Jeeez, all these years - and Atlassian stills fails to support MarkDown...

[steve_pole]

I was actually mistaken - it's not Atlassian that updated their Dockerfile, but cptactionhank: https://hub.docker.com/r/cptactionhank/atlassian-jira/dockerfile

(who also sets the JIRA version explicitly, so the version is actually recognized in the marketplace - which then displays all the apps and doesn't fail with some miserable error message...)

I've worked with JIRA on Docker for a single day and fixed three easy to spot bugs that keep the app from working. That's a low, even for Atlassian.

No further comment.

[Tinker Fadoua]

@steve_pole Glad it is working for you.

[Dennis Jensch]

I had the same problem on Ubuntu 18.04 using the official docker-atlassian-jira image.

Will this problem be solved in the official Atlassian Jira image? Or do I have to switch to other images if I don't want to modify the Dockerfile myself?

[insideAC]

+1
Will this be fixed?

[HDG]

+2

Atlassian newbie (trialing) - been struggling for the past few hours with fresh official Atlassian Docker Hub repos on Docker Desktop for Mac

• sometimes they run, sometimes they hang, sometimes they crash (particularly jira-servicedesk)
• jira-core and jira-servicedesk repo READMEs are copy/pasted from jira-software repo:

  docker run ... atlassian/jira-software

   (WRONG)
• no persistence though I am using

  -v jiraVolume:/var/atlassian/application-data/jira

  (per readme)
• not immediately clear how to run core+software+servicedesk in same container (had to google after trial/error/assumption that servicedesk included all of the above - why isn't there an jira-all repo?)
• 29 trial licenses generated because server IDs change on every reboot/crash
• third party repo has 5M pulls, vs official's 100K?
• BONUS: confluence readme uses bind mount instead of volume...
• BONUS2: no markdown!?  Do I really want to trial this anymore?
   

[VR]

Did someone get past with this error in container? Works in my mac docker local but not in container..Getting the same error and tried changing permission per https://confluence.atlassian.com/jirakb/jira-server-throws-unable-to-create-directory-for-deployment-error-on-startup-389781040.html and no luck. Using official docker image from atlassian.

[Dat Tang]

Why no one take care of this issue? I have the same issue.