[
https://issues.apache.org/jira/browse/MESOS-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878954#comment-15878954
]
Benjamin Bannier commented on MESOS-7156:
-----------------------------------------
{quote}
No promises, but if I was to implement support for this in the Docker
containerizer, is that something that would be likely to be accepted? For now,
I'm just using DockerInfo.parameters, but I'd like to eventually be
future-proofed against that field going away.
{quote}
That's something that would definitely be welcomed with open arms! While
{{DockerInfo.parameters}} allows to pass on extra flags, it isn't a very well
abstracted way to go about it (well, it's just a hack with zero abstractions),
and it also makes it harder than necessary to switch containerizers. I believe
adding support for this to {{Docker::RunOptions::create}} should not be hard.
> Docker containerizer ignores capability requests
> ------------------------------------------------
>
> Key: MESOS-7156
> URL: https://issues.apache.org/jira/browse/MESOS-7156
> Project: Mesos
> Issue Type: Bug
> Components: containerization, documentation
> Affects Versions: 1.1.0
> Environment: Ubuntu 16.04
> Reporter: Bruce Merry
> Priority: Minor
>
> I'm trying to set a capability (SYS_NICE) by populating the
> linux_info.capability_info.capabilities field in a ContainerInfo, while using
> the Docker containerizer. I was expecting this to turn into a `--cap-add`
> argument passed to Docker, but in fact nothing happens. I also grepped the
> source of Mesos HEAD and there doesn't seem to be any code to pass --cap-add.
> Maybe this is intended, but I couldn't find anything to indicate this in the
> documentation or in mesos.proto, and the placement of linux_info in
> ContainerInfo rather than in MesosInfo led me to expect that it would be
> supported independently of the containerizer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
