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
My environment consists of a local development workstation and a Docker host that has had some hardening applied.
By default, new files and directories are created following the UMASK 077 directive in the /etc/login.defs file.
Without updating permissions on the app/scripts/init-db directory, docker compose fails to start the container stack. The resulting error is thrown by the plandex-postgres container:
plandex-postgres-1 | ls: cannot open directory '/docker-entrypoint-initdb.d/': Permission denied
Expected result
The start_local.sh script should check and prompt/force update permissions to the init-db directory, otherwise, reflect this necessary requirement appropriately in documentation for others who run into the same permissions issue.
Workarounds
A simple chmod -R 0755 init-db was sufficient enough to allow docker compose to bring up the Postgres container.
The text was updated successfully, but these errors were encountered:
Describe your issue
My environment consists of a local development workstation and a Docker host that has had some hardening applied.
By default, new files and directories are created following the UMASK 077 directive in the
/etc/login.defs
file.Without updating permissions on the
app/scripts/init-db
directory, docker compose fails to start the container stack. The resulting error is thrown by the plandex-postgres container:plandex-postgres-1 | ls: cannot open directory '/docker-entrypoint-initdb.d/': Permission denied
Expected result
The start_local.sh script should check and prompt/force update permissions to the
init-db
directory, otherwise, reflect this necessary requirement appropriately in documentation for others who run into the same permissions issue.Workarounds
A simple
chmod -R 0755 init-db
was sufficient enough to allow docker compose to bring up the Postgres container.The text was updated successfully, but these errors were encountered: