Dockerize Jira Software upgrade

Kentra Technologies

Hi, we are currently using Atlassian Jira Software + Service Desk docker containers. We want to do a normal image upgrade. To do that, we followed your instructions:

• Creating a volume for the container
• Removing container
• Download last version (or required version) of the new image
• Run docker container again

Problems:

• Inside the container, I have to manually configure dbconfig.xml to access the database. Is this the usual procedure?
• I lost all my Jira plugins, manually configuring dbconfig.xml, using docker volume, I have access to Jira data, but I lost all my Jira plugins and issues attachments. I have to manually install all Jira plugins once more. Is that the usual procedure for a Jira Software docker container image upgrade?
• I lost issue attachments. I notice that I lost all attachments. What do I have to do to save and don't lose all these work?
• I notice that Docker is creating a volume 

  af570ca0cb07095866d49e569b4b949275218ecda4ee31b78afbe6bd37bacb5a that I don't understand what it is. It seems that is a temporary volume, besides the one I had created before. What is this volume for? how do I named it, beside data?

My docker install statements were:

1. sudo docker volume create --name jira3Volume
2. sudo docker volume create --name jira3LogsVolume

3. sudo docker run --mount source=jira3Volume,destination=/var/atlassian/application-data/jira3  --mount source=jira3LogsVolume,destination=/var/atlassian/application-data/jira3logs --name=jira3 --network kentra.atlassian.network -d -p 8084:8084 -e ATL_TOMCAT_PORT=8084   atlassian/jira-software

What am I doing wrong in order do lose my Jira Plugins, all the attachments, don't be able to name the required Docker volumes and have to manually configure dbconfig.xml again?

Can you please help?

thanks in advance

Daniel Eads

Hi there,

The plugins, attachments, and dbconfig.xml are all stored in jira's home directory. From the description of what seems to have happened with your upgrade, it sounds like that directory wasn't mounted to the container in the way that was necessary for Jira to access it.

If you ran those docker create statements prior to launching the new docker image, I think the issue is that you simply created a blank volume, and mounted that. Unless something happened between the create and the run, I don't see where the data from the previous installation's home directory would have been copied in.

You could use this command to look at that docker mountpoint to get the actual file path on disk:

sudo docker volume inspect jira3Volume

If the dbconfig.xml file in that directory is the one you just set up, or there's no attachments when you drill down into the attachments directory in that path, having "a blank home directory" when starting your new Jira docker container is the culprit.

Assuming that's the case, if you can locate your previous installation's home directory on disk, you could copy the contents into the new jira3Volume mount directory.

Let me know if you need help with what to do once the previous home directory is located.

Cheers,
Daniel