Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container should survive restart #50

Open
rubiktubik opened this issue Dec 19, 2018 · 3 comments
Open

Container should survive restart #50

rubiktubik opened this issue Dec 19, 2018 · 3 comments

Comments

@rubiktubik
Copy link

rubiktubik commented Dec 19, 2018

Hi, awesome docker-image! But i need to mount the jira specific folders so that if the container is restarted all data is not lost.

How do you handle persistent data?
Some data is in the DB but if i restart the container i need to configure it again. And my previous data seems lost.

Regards
rubiktubik

@viceice
Copy link

viceice commented Dec 20, 2018

You have to mount a local folder or a docker volume.

# Set volume mount points for installation and home directory. Changes to the
# home directory needs to be persisted as well as parts of the installation
# directory due to eg. logs.
VOLUME ["/var/atlassian/jira", "/opt/atlassian/jira/logs"]

@rubiktubik
Copy link
Author

This setting is the default or i'am wrong? When i restart the container i need to do the setup again.

@viceice
Copy link

viceice commented Dec 21, 2018

By default, docker will assing only temporary volumes, wich will be deleted after container recreation.
If you only restart, aka docker restart jira, then the data will survive.

So, if you want to retain the data, you have to explicitly mount a local folder or a docker volume. See https://docs.docker.com/engine/reference/run/#volume-shared-filesystems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants