I need to install onlyoffice workspace, this is a Docker app and requires to be installed in /app, i appreate why / is RO, yet sudo mount -o rw,remount / does not work and this is a key app for me
/ is read-only by design and cannot be remounted RW. You cannot create /app or bind-mount anything under /, even as root.
Correct approach:
Put data on /DATA (for example /DATA/AppData/onlyoffice)
Map it in Docker as:
Host: /DATA/AppData/onlyoffice
Container: /app
Docker does not require /app to exist on the host.
If the OnlyOffice image requires a writable host /app, it’s not immutable-OS friendly. In that case, use a different image, override paths, or run it in a VM.
Nothing is broken, this is how ZimaOS is designed.
the only officeworkspace installer puts all data on /app i have tried to alter by hand and it just doesnt work, they have designed it way. i was hopeing that i could put the OS into rw mode so i could create the /app directory then map it to my NVME drive, then place the OS ro again.
i currently have it running on a VM and in fairness it works issue is size.
i didnt want on the new box to go vm route as i wanted in fairness to be able to use all my storage array, and not have to have either a, a huge 4 tb vm or b, a vm with smb connected to the underlying storage array.
here is the installer if you thing there is a way of adjusting to work
You’re right, OnlyOffice Workspace is hard-coded for a traditional RW Linux root and assumes it can create /app on the host. That installer is not compatible with ZimaOS.
ZimaOS cannot be switched to RW, even temporarily. / is immutable by design, so creating /app or bind-mounting NVMe there is impossible.
This isn’t a ZimaOS bug, it’s a Workspace installer limitation.
Realistic options:
Keep running Workspace in a VM (correct but storage-heavy), or
Use OnlyOffice Docs (DocumentServer) in Docker, which works properly with /DATA mappings.
There’s no safe workaround to make the Workspace installer work directly on ZimaOS.