Since the update to ZimaOS v1.6, network units mounted via the "Add LAN Storage" UI are suffering from a permission mismatch when accessed by Docker containers (specifically qBittorrent, but affecting others). Although the host (root) has write access, containers running as non-root users (UID 1000) or even as root with PUID/PGID=0 receive a "Permission Denied" error when attempting to write to the mount point.
Technical Details:
Host OS: ZimaOS v1.6 (Immutable root filesystem).
Path: /media/unasbox/[ResourceName]
Observation 1: The chmod -R 777 command fails to change permissions on the mount point as it is ignored by the CIFS driver.
Observation 2: The root filesystem is mounted as Read-only, preventing the creation of manual mount points in /mnt or / to bypass the UI management.
Observation 3: Local USB drives do NOT exhibit this behavior, confirming the issue is specific to the CIFS/SMB mounting parameters used by the ZimaOS storage manager.
Suspected Root Cause:
The ZimaOS storage manager appears to be mounting network shares without the necessary flags for Docker interoperability. Specifically, the lack of uid, gid, file_mode=0777, dir_mode=0777, or noperm flags in the internal mount command is causing a kernel-level block for containerized processes.
Requested Fix:
Please allow users to specify UID/GID or Masks in the LAN Storage settings, or ensure that network mounts in /media are mounted with more permissive flags (e.g., noperm, serverino) to allow Docker containers to write to them without "Permission Denied" errors.
Since the update to ZimaOS v1.6, network units mounted via the "Add LAN Storage" UI are suffering from a permission mismatch when accessed by Docker containers (specifically qBittorrent, but affecting others). Although the host (root) has write access, containers running as non-root users (UID 1000) or even as root with PUID/PGID=0 receive a "Permission Denied" error when attempting to write to the mount point.
Technical Details:
Host OS: ZimaOS v1.6 (Immutable root filesystem).
Path: /media/unasbox/[ResourceName]
Observation 1: The chmod -R 777 command fails to change permissions on the mount point as it is ignored by the CIFS driver.
Observation 2: The root filesystem is mounted as Read-only, preventing the creation of manual mount points in /mnt or / to bypass the UI management.
Observation 3: Local USB drives do NOT exhibit this behavior, confirming the issue is specific to the CIFS/SMB mounting parameters used by the ZimaOS storage manager.
Suspected Root Cause:
The ZimaOS storage manager appears to be mounting network shares without the necessary flags for Docker interoperability. Specifically, the lack of uid, gid, file_mode=0777, dir_mode=0777, or noperm flags in the internal mount command is causing a kernel-level block for containerized processes.
Requested Fix:
Please allow users to specify UID/GID or Masks in the LAN Storage settings, or ensure that network mounts in /media are mounted with more permissive flags (e.g., noperm, serverino) to allow Docker containers to write to them without "Permission Denied" errors.