Storage Permission Errors

Storage Permission Errors

PalCenter runs as a non-root user and requires read/write access to /app/data. It does not take ownership of host directories at startup.

Check the configured identity

With Compose:

docker compose config

Look for:

user: 1000:1000

Check the running process:

docker compose exec palcenter id

The standard deployment uses UID/GID 1000:1000. Unraid normally uses 99:100.

Named volume

Use 1000:1000 with the default palcenter-data Docker volume. Avoid changing UID/GID on an existing volume unless its ownership already matches the new identity.

Bind mount

For a host path such as:

volumes:
  - /srv/palcenter:/app/data

the selected container UID/GID must be able to create, read, update, rename, and delete files in /srv/palcenter.

PalCenter may warn if the host filesystem refuses permission tightening while still allowing normal reads and writes. That warning is safe to review. A failure stating that storage is not writable must be fixed on the host.

Do not solve permission errors by running PalCenter as root, enabling privileged mode, or granting extra capabilities.

For Unraid, see Unraid Deployment.