enhancement - docker access mode for unassigned devices


Recommended Posts

When editing docker volumes in advanced mode, our "access mode" setting includes six options:

  • Read Write (private)
  • Read Write shared
  • Read write slave
  • Read Only (private)
  • Read Only shared
  • Read Only slave


I believe that all six are valid for host paths that are on the array or cache drive, but only the shared/slave bind propagation options are valid for unassigned devices.


Can we add smarts to the webgui to handle this?

  • In advanced editing mode - if the selected host path is under /mnt/disks/ (i.e. an unassigned device) the "private" options should be suppressed.  
  • In basic editing mode - since the settings are not visible, if the selected host path is under /mnt/disks/ it should automatically use "slave" (or "shared"?) 


This will eliminate problems related to docker not being able to access files on unassigned devices.

In terms of documentation, this page describes how to mount volumes:
and descriptions of private/slave/shared are here:


Interestingly, it seems like "shared" might be the most flexible mode of all.  I wonder if it should be the default everywhere?

Link to comment
  • 1 year later...
  • 8 months later...
  • 2 years later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.