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
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/9.5/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
creating template1 database in /var/lib/postgresql/9.5/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
loading PL/pgSQL server-side language ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
syncing data to disk ... ok
Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/9.5/data -l logfile start
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
check for "/var/lib/postgresql/9.4/data/base" failed: No such file or directory
Failure, exiting
Error message
check for "/var/lib/postgresql/9.4/data/base" failed: No such file or directory
Failure, exiting
I'm almost sure that the root cause of the issue is the owner of the docker host directories.
The start of the workaround will require re-building a custom image with something like below:
ARG GNAME='groupname'
ARG GID=123
ARG USERID=113
# fix permissions so it can persist data on the host nfs file system
RUN groupadd -g $GID $GNAME \
&& usermod -g $GNAME postgres \
&& usermod -u $USERID postgres
The text was updated successfully, but these errors were encountered:
I run into the same issue when upgrading from 10 to 12
Same here, and I can confirm the file /var/lib/postgresql/10/data/PG_VERSION really exists:
`The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/12/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
Success. You can now start the database server using:
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
could not open version file "/var/lib/postgresql/10/data/PG_VERSION": No such file or directory
Failure, exiting`
Hi there.
First of all many thanks to all the people involved in this project for their time.
I'm trying to follow the provided example in the README, and I get an error.
Steps to reproduce
Expected behaviour
See a success message in the standard out
Found behaviour
The process stopped with an error message:
Error message
Additional information
I'm almost sure that the root cause of the issue is the owner of the docker host directories.
The start of the workaround will require re-building a custom image with something like below:
The text was updated successfully, but these errors were encountered: