You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I must be the nth person asking for this, but I can find a solution for this anywhere.
Since, as per the doc, 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,it seems there is no way to add a script to /docker-entrypoint-initdb.d to create a new User/Database couple when you add, say a new container to a docker-compose file and want to share a single postgres instance.
Or am I understanding this wrong?
In anycase, in my tests I get a PostgreSQL Database directory appears to contain a database; Skipping initialization in the logs, confirming the behaviour.
The text was updated successfully, but these errors were encountered:
See #929, #173, #821, #191 (to link a few similar issues) -- hopefully one of these has some helpful clues for helping you implement what you're looking for 👍
I must be the nth person asking for this, but I can find a solution for this anywhere.
Since, as per the doc,
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
,it seems there is no way to add a script to/docker-entrypoint-initdb.d
to create a new User/Database couple when you add, say a new container to a docker-compose file and want to share a single postgres instance.Or am I understanding this wrong?
In anycase, in my tests I get a
PostgreSQL Database directory appears to contain a database; Skipping initialization
in the logs, confirming the behaviour.The text was updated successfully, but these errors were encountered: