lelii
/
hf-storage-data
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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 <noreply@anthropic.com>
This commit is contained in:
Lucio Lelii 2026-10-02 10:33:23 +02:00
parent c018adf25d
commit 169ad32f0b
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.env.example
View File

@ -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=