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
FlowDB currently takes two build arguments POSTGRES_UID and POSTGRES_GID which were necessary to enable one to work around conflicts between the user Postgres ran as, and the uids on the host system. Per docker-library/postgres#253 and docker-library/postgres#448 the upstream image now supports setting these via --user to match an existing user on the host system. Using this method also means docker won't clobber permissions when spinning up the Postgres instance if you don't have a user matching the internal uid & gid.
We should remove the old workaround, and explain how to do this in the docs.
The text was updated successfully, but these errors were encountered:
FlowDB currently takes two build arguments
POSTGRES_UID
andPOSTGRES_GID
which were necessary to enable one to work around conflicts between the user Postgres ran as, and the uids on the host system. Perdocker-library/postgres#253 and
docker-library/postgres#448 the upstream image now supports setting these via
--user
to match an existing user on the host system. Using this method also means docker won't clobber permissions when spinning up the Postgres instance if you don't have a user matching the internal uid & gid.We should remove the old workaround, and explain how to do this in the docs.
The text was updated successfully, but these errors were encountered: