How to authorize the application installed to have the authorization to make chage on my main storage and not only the installation disk?

Insight & Feedback
1

How to authorize the application installed to have the authorization to make chage on my main storage and not only the installation disk?

Currently the intalled applications do not have the authorization to make changes (erase file, create folders …. on my main storage disk which is a raid 5)

2

What you’re seeing is normal and expected behaviour in ZimaOS.

ZimaOS (built on CasaOS with added NAS features like RAID) intentionally restricts apps.
Apps installed from the App Store (Docker containers) have full read/write access only to their own AppData on the install disk.

For other storage (RAID 5, extra disks, USB drives), apps get read access only by default. Write actions (create, delete, rename) are blocked unless ownership is applied correctly.

Why terminal fixes usually don’t work

Manual chmod / chown, Portainer edits, or app reinstalls often don’t persist due to how ZimaOS handles mounts and container permissions.

The recommended fix (no terminal)

This is the most reliable, community-verified solution:

  1. Open the Files app in ZimaOS
  2. Go to your main storage / RAID
  3. Create a new folder there
    4.or move the existing folder somewhere else and move it back*
  4. Use that folder in your app settings

Creating or “touching” the folder via the Files app applies the correct ownership, and the app will immediately be able to write, delete, and modify files.

Note

  • Applies to almost all apps
  • PUID/PGID tweaks can help in some cases, but the Files method is simpler and more reliable
  • Not well documented yet, but consistently confirmed by the community

If it still doesn’t work after this, share the app name and error and we can dig deeper.

3

Hi George,

Unfortunately, it is still not working.

The app is SFTPGO. As suggested I created the folder “srv” and sub folder “data” in my Main storage (raid5) through file and using Parameters point to it instead of the folder SRV in ZimaOs HD. But when I am creating a new user and I try to create a folder for him or to upload a document I have the message Error creating new folder. Permission denied or Error uploading document and it is linked to the fact that SFTPGO has not the right to modify on the Main Storage (Raid5).

Same issue with Navidrome, I have my music on the folder “Media”/”Music” that I moved to the main storage, but I cannot erase a song from Navidrome as the app tells me that it does not have the right to modify on this folder.

Do n ot hesitate to ask If I am not clear.

Regards

Freneuilg

4

Thanks for the detailed explanation, that clarifies things.

What you’re seeing is not a general ZimaOS permission issue, but app-specific behaviour.

The Files-app “create or move folder” method only fixes filesystem ownership. It does not override how a container itself is designed to access data.

In your cases:

SFTPGo
SFTPGo enforces its own internal permissions and runs as a non-root user.
When you point it to a RAID path, it can read it, but it often cannot create or delete files unless the path fully matches what the app expects. This is a known limitation and not something ZimaOS can force.

Navidrome
Navidrome is read-only by design. It scans music libraries but does not manage files.
Deleting or modifying tracks from inside Navidrome is not supported, regardless of storage location.

So in short:

  • ZimaOS permissions are working correctly
  • The limitation comes from how these apps are built

Recommended approach:

  • Use ZimaOS Files (or a file-manager app) to manage files
  • Use SFTPGo only for uploads/downloads to a dedicated folder
  • Treat Navidrome as read-only and manage music outside it

Nothing is broken, it’s just app design limits.