Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Need an option to always import files in /docker-entrypoint-initdb.d #58

Closed
poagester opened this issue Mar 12, 2018 · 3 comments
Closed
Labels
Request Request for image modification or feature

Comments

@poagester
Copy link

our build process has no way to clean the mounted volume for the databases. sometimes we need to persist them, which is perfect already. other times we want to re-run the scripts to drop and re-create all databases. Currently there does not seem to be a way to work around this, is this feasible to work in and is there a way we can work around this for the time being?

@poagester
Copy link
Author

Something similar to this:
I have created a new function to inject the files in the init.d folder and introduced a new variable for the environment named RESTORE_DATABASES, that if set to 1 will call the function. My syntax may not be 100% correct, but it's just an example that I think a lot of other users may find really helpfull.

entry_point.txt

@poagester
Copy link
Author

poagester commented Mar 13, 2018

i have attached a completed docker-entrypoint.sh.txt file which introduces a new environment variable to determine if the user would like to re-inject the sql files. Please let me know the best way to contribute these changes.
docker-entrypoint.sh.txt

@wglambert wglambert added the Request Request for image modification or feature label Apr 25, 2018
@yosifkit
Copy link
Member

yosifkit commented Nov 28, 2018

The percona official image is no longer maintained in this repository and is now maintained by Percona LLC -- please see https://hub.docker.com/_/percona/ for details about the new home of the percona official image source.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Request Request for image modification or feature
Projects
None yet
Development

No branches or pull requests

3 participants