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'm using the latest timescale/timescaledb-ha:pg16.2-ts2.14.2-all Docker image, but I'm still getting the
initdb: error: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted
fixing permissions on existing directory /var/lib/postgresql/data ... %
error like in issue #359 when providing the PGDATA env variable.
Like described in this reply #359 (comment), a workaround is to provide a local path for the volume and to manally set the permissions. And when I do it like this it works.
But that doesn't work when you want to let docker handle the directory.
Also I have noticed that when ever I run docker compose down and docker compose up a new anonymous volume is created. Even though I have provided a named volume in the dockercompose file and this is actually being used.
The text was updated successfully, but these errors were encountered:
I'm using the latest
timescale/timescaledb-ha:pg16.2-ts2.14.2-all
Docker image, but I'm still getting theerror like in issue #359 when providing the
PGDATA
env variable.My docker-compose config looks like this:
Like described in this reply #359 (comment), a workaround is to provide a local path for the volume and to manally set the permissions. And when I do it like this it works.
But that doesn't work when you want to let docker handle the directory.
Also I have noticed that when ever I run
docker compose down
anddocker compose up
a new anonymous volume is created. Even though I have provided a named volume in the dockercompose file and this is actually being used.The text was updated successfully, but these errors were encountered: