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

Data Persistence #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Data Persistence #3

wants to merge 1 commit into from

Conversation

BarnumD
Copy link

@BarnumD BarnumD commented Oct 16, 2016

I made a version that, sensing a volume at /data, manages the mysql datadir in that location. Except, each container gets it's own subfolder. That way you can have multiple containers on each host. Or all the containers can share a network (nfs) location safely. There is also a cleanup function as containers come and go. I'll put in a pull request.
Fixes Issue #2

@BarnumD BarnumD changed the title Datavol Data Persistence Oct 16, 2016
Add data persistence option.
Adjust readme for data persistence.
@valentin2105
Copy link

valentin2105 commented Nov 8, 2016

I just tested this configuration and it work fine. Thanks @BarnumD and @toughIQ

You can also pull this image in valentinnc/mariadb-galera:10.1

an example with Wordpress here : https://gist.github.com/valentin2105/9c6abe0acc9a05ca0fa3abbf830d80a6

@pascalandy
Copy link

Keeping an eye on this :)

@dottgonzo
Copy link

consider in addition the ability to restore the db from a backup file at boot

@dottgonzo
Copy link

after some days in a swarm environment, i can say that the choice to not use persistent volumes is right. Trying to syncronize persistent volumes with gluster cause slow performances, and have many replicas is just enought

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

Successfully merging this pull request may close these issues.

5 participants