From: | Jorge Torralba <jorge(dot)torralba(at)gmail(dot)com> |
---|---|
To: | John Scalia <jayknowsunix(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Option to make PostgreSQL quiescent on startup? |
Date: | 2017-12-08 22:52:08 |
Message-ID: | CACut7uSSeWiejZ7bJXZYnHJvRo75izYsqABZ_ERCRKuN6JjS8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Does the container stop? Try docker exec -it container /bin/bash and see if
you can evaluate there. You can also do docker logs to see what is
happening.
On Dec 8, 2017 2:14 PM, "John Scalia" <jayknowsunix(at)gmail(dot)com> wrote:
Hi all,
I have been trying to get a new Docker container working with PostgreSQL
9.6.6 and I’d like it to start with one of our app’s schemas, but the shell
script I’m invoking at the end of the Dockerfile with an ENTRYPOINT doesn’t
seem to want to go past the database startup. I think the script isn’t
completing due to the output of postgres process. At least, this is my
suspicion. Right now, the shell script is only trying to invoke psql -c
“CREATE DATABASE code” after it starts the cluster. If this is the case, is
there any option to just quietly start the cluster? If not, is there anyway
to make this work?
—
Jay
Sent from my iPad
From | Date | Subject | |
---|---|---|---|
Next Message | Marcelo Kruger | 2017-12-10 21:59:36 | Re: [ADMIN] High replication lag - Stream Replication |
Previous Message | John Scalia | 2017-12-08 22:14:23 | Option to make PostgreSQL quiescent on startup? |