From 169ad32f0bebd404db77091093cf3a24d50d588f Mon Sep 17 00:00:00 2001 From: Lucio Lelii Date: Fri, 2 Oct 2026 10:33:23 +0200 Subject: [PATCH] Make clear that the data path variables take only a path The example put "owner 1000:1000" on the same line as MINIO_DATA_PATH, which reads as part of the value and, pasted into .env, would make the compose look for a directory with that odd name. The paths and the chown commands are now on separate lines, with the reason the owner is a number: it is the container's user, not whoever runs docker. Co-Authored-By: Claude Sonnet 5.5 --- .env.example | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/.env.example b/.env.example index c1e2cdf..6a46de1 100644 --- a/.env.example +++ b/.env.example @@ -37,8 +37,12 @@ POSTGRES_IMAGE=postgres:17.11-alpine # /var/lib/docker. To use a larger disk, give an absolute path to a directory ON it - a # subdirectory, never the mount point itself, which on ext4 holds lost+found and makes PostgreSQL # refuse to start. Create the directories and set their owner first; see "Storing the data on -# another disk" in the README. -# POSTGRES_DATA_PATH=/mnt/bigdisk/postgres owner 70:70, mode 700 -# MINIO_DATA_PATH=/mnt/bigdisk/minio owner 1000:1000 +# another disk" in the README. Only the path goes in the value: +# POSTGRES_DATA_PATH=/mnt/bigdisk/postgres +# MINIO_DATA_PATH=/mnt/bigdisk/minio +# The owner is set on the host directory, by number, because that is what the container's user +# is: the user inside the container, not whoever runs docker. +# sudo chown 70:70 /mnt/bigdisk/postgres && sudo chmod 700 /mnt/bigdisk/postgres +# sudo chown 1000:1000 /mnt/bigdisk/minio POSTGRES_DATA_PATH= MINIO_DATA_PATH=