-
Notifications
You must be signed in to change notification settings - Fork 649
docker-entrypoint-initdb.d not working #200
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
Comments
Did you start it once and then change scripts and environment variables? It is probably the same as docker-library/postgres#203 (comment). |
Yep that was it thank you. Maybe an environment variable could be added which allows this to be forced if required without rebuilding the container? As per this Oracle container. https://hub.docker.com/r/sath89/oracle-12c/ IMPORT_FROM_VOLUME=true |
The root of this issue was solved. If you would like to discuss a way to force import scripts, I think that should be a new issue. |
I think this issue should be re-opened. I can't get anything to execute in /docker-entrypoint-initdb.d. I've deleted volumes, deleted and re-created containers and images, deleted mong-seed on the host and nothing. My compose is dead simple:
In the mongo-seed directory, I have seed-data.js which just contains:
I've used the same procedure with the MySQL image without issue. |
Ah, thank you. I am using 3.2.9 because that's the default for dokku. |
I'm using mongo:3.2
This is my docker compose file
This is my bash script contained in my local ./databaseInit/mongoDB folder
#!/usr/bin/env bash mongorestore --gzip --archive=./backups/prod_backup_20170704 --db amp_blue_syd
When I run docker-compose build and or docker-compose up, there is no mention of the entrypoint.sh script attempting to execute my script. Can you let me know what I'm doing wrong?
The text was updated successfully, but these errors were encountered: