how to I use the CLI to mount a volume as read-only?

[jdef]

No description provided.

[clintkitson]

@jdef Can you describe how you are using dvdcli? Is it in combination with the mesos-module-dvdi? Currently mount options are not configurable.

In the case of using it with Mesos, this could be something that is added as a volume option. It would be respected during the bind mount into the container that Mesos starts.

More information about how you are using it would help steer the conversation.

[jdef]

the use case I had in mind was mounting the same "shared" vol instance on
multiple hosts as RO. so they'd be mounted on each host as RO and also
mounted in each container as RO

On Thu, Mar 17, 2016 at 3:16 PM, Clinton Kitson [email protected]
wrote:

@jdef https://github.com/jdef Can you describe how you are using dvdcli?
Is it in combination with the mesos-module-dvdi? Currently mount options
are not configurable.

In the case of using it with Mesos, this could be something that is added
as a volume option. It would be respected during the bind mount into the
container that Mesos starts.

More information about how you are using it would help steer the
conversation.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#15 (comment)

James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)

[vladimirvivien]

@jdef long time! I am part of the emc {code} team working on this. Anyway, the dvdi-module ultimately mounts the vol on the container using Docker's plugin api underneath. Right now, there's no option to enforce readonly in Docker volume plugin, therefore, there's no way to enforce this.

Keep in mind this project is the dvdicli, there's also the mesos-dvdi-module which works as a mesos module to do volume management - https://github.com/emccode/mesos-module-dvdi.

Let us know if you have more questions.

[jdef]

Hi Vladimir! I had started digging through the docker code to check whether
this was possible, but was side-tracked. You've answered that question for
me. I haven't played around very much with these drives on the docker
command line but it seems strange that Docker would mount something on the
host as RW if I specified something like -v
myVolName:/path/in/container:ro. But I can think of situations where RW
mounting on the host, and then binding w/ RO in a container is useful as
well. Probably need to think about our (future) use cases some more.

Any way, even if RO isn't supported at the host level I think it makes
sense as something to support at the container level - and that sounds like
a feature for the mesos module.

On Mon, Mar 21, 2016 at 6:07 PM, Vladimir Vivien [email protected]
wrote:

@jdef https://github.com/jdef long time! I am part of the emc {code}
team working on this. Anyway, the dvdi-module ultimately mounts the vol on
the container using Docker's plugin api underneath. Right now, there's no
option to enforce readonly in Docker volume plugin, therefore, there's no
way to enforce this.

Keep in mind this project is the dvdicli, there's also the
mesos-dvdi-module which works as a mesos module to do volume management -
https://github.com/emccode/mesos-module-dvdi.

Let us know if you have more questions.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#15 (comment)

James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)