fix: resolve Docker Compose permission denied errors for mounted volumes

[roman98Z]

Fix: Resolve Docker Compose Permission Denied Errors

Overview

This Pull Request addresses issue #591 by fixing the "permission denied" errors that occur when running Docker Compose with mounted volumes.

Problem

When users attempt to run the indexer using Docker Compose:

docker compose --profile cloud up

They encounter permission denied errors because:

1. The postgres and nats containers run as internal users (postgres user, nats user)
2. These internal users have different UID/GID than the host user
3. When mounting host directories (./target/data/postgres, ./target/data/nats), the container cannot write to them due to ownership mismatch

This is a common Docker issue that affects many users, especially on Linux systems where file permissions are strictly enforced.

Solution

Added explicit user mapping to the affected services in docker-compose.yaml:

user: "${UID:-1000}:${GID:-1000}"

This configuration:

• Uses the UID and GID environment variables if set
• Falls back to 1000:1000 (common default for first user on Linux)
• Ensures containers run with the same permissions as the host user

Changes

docker-compose.yaml

Added user directive to:

• postgres service (line 129)
• nats service (line 152)

Added explanatory comments for clarity.

README.md

Added documentation in the "Using Docker Compose" section explaining:

• The permission handling mechanism
• How to set UID/GID environment variables
• Example commands for running Docker Compose

Usage

After this fix, users can run Docker Compose in two ways:

Option 1: Use defaults (works for most users)

docker compose --profile cloud up

Option 2: Explicitly set UID/GID (recommended)

export UID=$(id -u)
export GID=$(id -g)
docker compose --profile cloud up

Testing

This fix has been validated by:

1. Reviewing the Docker Compose configuration syntax
2. Verifying the user directive format is correct
3. Ensuring the environment variable substitution follows Docker Compose conventions

Impact

This is a non-breaking change that:

• Improves the developer experience for local development
• Reduces friction for new contributors
• Maintains backward compatibility (defaults to UID/GID 1000)

Related Issues

• Addresses Attempting to run with Docker Compose yields permission Denied #591 - Attempting to run with Docker Compose yields permission Denied

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Manus AI seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}