My n8n service stopped working after a container restart. The new n8n

image runs as a non-root user (UID 1000) but the existing files on my

persistent volume at /data/.n8n/ are owned by root from a previous

image version. The container can't read its own config file and

crash-loops with:

Error: EACCES: permission denied, open '/data/.n8n/config'

I've tried:

- Pinning to older n8n versions (1.68.0, 1.70.0) — same error

- Custom start command with chmod -R 777 /data — chmod fails silently

because the container has no write permission to root-owned files

- Removing custom start command — same EACCES error

I need the volume's ownership at /data reset to UID 1000:1000 (or

whatever the current n8n image expects) so the container can read

its own files.

Project ID: db6be71f-bd3c-410e-9bcc-d4aea4b231e4

Service ID: 19bb1afb-3666-41ed-9575-268a92999ca4

Environment ID: 2db08a78-2ec2-4050-9ded-8ef717b15265

Volume: n8n-volume

This is blocking my production workflow automation. All my data is

intact on the volume — I just need read/write access restored.