Initialization scripts
If you would like to do additional initialization in an image derived from this one, add one or more *.sql, *.sql.gz, or *.sh scripts under /docker-entrypoint-initdb.d (creating the directory if necessary). After the entrypoint calls initdb to create the default postgres user and database, it will run any *.sql files, run any executable *.sh scripts, and source any non-executable *.sh scripts found in that directory to do further initialization before starting the service.
Warning: scripts in /docker-entrypoint-initdb.d are only run if you start the container with a data directory that is empty; any pre-existing database will be left untouched on container startup. One common problem is that if one of your /docker-entrypoint-initdb.d scripts fails (which will cause the entrypoint script to exit) and your orchestrator restarts the container with the already initialized data directory, it will not continue on with your scripts.
Initialization scripts
If you would like to do additional initialization in an image derived from this one, add one or more
*.sql,*.sql.gz, or*.shscripts under/docker-entrypoint-initdb.d(creating the directory if necessary). After the entrypoint calls initdb to create the default postgres user and database, it will run any*.sqlfiles, run any executable*.shscripts, and source any non-executable*.shscripts found in that directory to do further initialization before starting the service.Warning: scripts in
/docker-entrypoint-initdb.dare only run if you start the container with a data directory that is empty; any pre-existing database will be left untouched on container startup. One common problem is that if one of your/docker-entrypoint-initdb.dscripts fails (which will cause the entrypoint script to exit) and your orchestrator restarts the container with the already initialized data directory, it will not continue on with your scripts.