[
https://issues.apache.org/jira/browse/MESOS-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878725#comment-15878725
]
Benjamin Bannier commented on MESOS-7156:
-----------------------------------------
Currently, only the Mesos containerizer supports Linux capabilities and adding
support to the Docker containerizer is not planned. The chosen protobuf
definition would allow for this though (this is also true for e.g., the
{{network_infos}} and {{rlimit_info}} fields).
The way we choose to document this is to explicitly call out supported fields
in the documentation for the Docker or Mesos containerizer, instead of
documenting ignored fields. While this approach probably requires consulting
the documentation in addition to the protobuf definitions, I believe it helps
to keep the documentation readable by not documenting irrelevant fields in
their full combinatorial complexity.
> 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)
