Support for docker volume ":ro" or ":readonly" usage like decribed in docker docs

Insight & Feedback
1

Support for docker volume “:ro” or “:readonly” usage like described in docker docs

seems like the webui when changing the volumes it does not see the :ro “tag” last

image

2

I believe this is a current limitation of the ZimaOS WebUI, not Docker itself.

Docker fully supports :ro / readonly bind mounts, but the ZimaOS UI does not parse or preserve the :ro suffix when editing volumes. When you save or reopen the container, the UI rewrites the mount and silently drops the flag.

I suggest one of these workarounds for now:

  • Create or edit the container using Docker CLI or docker-compose, where :ro is respected.
  • Treat the WebUI as write-only for volumes once the container is created.
  • Avoid reopening the volume editor if read-only mounts matter.

I think proper read-only support needs to be added at the UI validation layer, not Docker. This is a good feature request.

3

true though i think it should explain that when using it..

i would think it (webui) should have a view of the compose file or run cmd line so people could see what it’s actually is doing.. like it is now, it could be hard to debug issues..

in short a “view hole docker commands” link or a like..

4

editor for the app like viewing the hole docker file/cmd/compose should be included.

5

In future WebGUIs we will have more options in the editor. Everything is in the process of being designed.

1 Like