You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For many of my apps, (grocy inclusive) I use NFS mounts to mount in the /config directory.
This works fine normally, when the target directory is owned by the same UID/GID as mentioned in the PUID and GUID variables. On the NFS server side, I also map all users to that UID/GID via NFS.
Barcodebuddy could successfully create the data and keys directory, so the permissions are correct, but fails to chown /app/bbuddy/data:
barcodebuddy-1 | Barcode Buddy supervisor started
barcodebuddy-1 |
barcodebuddy-1 | Initialising container
barcodebuddy-1 | 2024/09/18 17:36:38 chown /app/bbuddy/data: operation not permitted
barcodebuddy-1 exited with code 0
This is the section from my docker compose yaml, that relates to barcode buddy:
For many of my apps, (grocy inclusive) I use NFS mounts to mount in the
/config
directory.This works fine normally, when the target directory is owned by the same UID/GID as mentioned in the
PUID
andGUID
variables. On the NFS server side, I also map all users to that UID/GID via NFS.Barcodebuddy could successfully create the
data
andkeys
directory, so the permissions are correct, but fails tochown /app/bbuddy/data
:This is the section from my docker compose yaml, that relates to barcode buddy:
.env
file:The text was updated successfully, but these errors were encountered: