This is part of my initdb.sh: #!/bin/bash Btw, I read here that the container shutting down and restarting is (apparently) part of the initialization process. I had the same issue but after a few hours of trying, I found a working combination of docker-compose and init script. GRANT ALL PRIVILEGES ON DATABASE audit_service to "postgres" I struggled with this same issue and thought the only solution was to not use a sql file in the docker-entrypoint-initdb.d directory but actually the only problem was that I wasn't granting pivs to my user i was logging in as so the schemas were getting created just invisible to my user. initdb.sh:/docker-entrypoint-initdb.d/initdb.sh This is part of my docker-compose.yml: version: '3.7'
Kitematic start a postgres 9.4 container password#
Psql -v ON_ERROR_STOP=1 -username "$POSTGRES_USER" -d "$POSTGRES_DB" <<-EOSQLĬreate role $AUTHENTICATOR noinherit login password '$POSTGRES_PASSWORD' When I get a shell into my db container, the database rivers was created but is empty, with no tables, relations, or data from my batched inserts.
17:43:06.637 UTC LOG: aborting any active transactions Strends_psql | waiting for server to shut down. Strends_psql | 17:43:06.633 UTC LOG: received fast shutdown request Strends_psql | You are now connected to database "rivers" as user "usr". I'm running into an issue where my db init process is in fact running in the container, at least batching a bunch of CREATES and INSERTS of my dump data, but then is abruptly shut down and restarted.
0 kommentar(er)
