Hello community,
I recently migrated my external Apple HFS+ formatted hard drive from my Mac to my ZimaOS server and I am looking for some clarification on how HFS+ file structures are handled by the OS.
When I plug the drive into my ZimaOS machine, the native web-based Files app handles reading and writing seamlessly. I can move, delete, or modify files directly in the browser dashboard without any issues.
However, if I pass that same drive path into an isolated application space like a Docker container, or try to connect to the drive folder from a MacBook over a network share (SMB), I hit a strict read-only block.
From what I understand, this seems to happen because macOS configures HFS+ drives with journaling enabled by default. Does ZimaOS use special mounting flags to bypass the standard HFS+ write restrictions locally in the Files app, while isolated app containers and network sharing protocols default back to standard Linux kernel drivers that freeze the filesystem to read-only when active Apple journaling is detected?
Is this expected behavior for journaled HFS+ setups? If so, it would be really helpful if the official documentation clarified this journaling nuance with HFS drives since there appears to be a discrepancy between full write permissions in the Files app versus read-only blocks in app containers and network layers.