Hi Marc, > You also know how/where to put the capabilities? I am struggling > with that.
Have a look at the protobufs which define this API: * `TaskInfo` which is used with `mesos-execute` is defined here, https://github.com/apache/mesos/blob/558829eb24f4ad636348497075bbc0428a4794a4/include/mesos/mesos.proto#L2229-L2285, * capabilities are passed via a task’s `container` field, https://github.com/apache/mesos/blob/558829eb24f4ad636348497075bbc0428a4794a4/include/mesos/mesos.proto#L2239 which has a field `linux_info` whose structure is defined here, https://github.com/apache/mesos/blob/558829eb24f4ad636348497075bbc0428a4794a4/include/mesos/mesos.proto#L3270-L3341 * in there you want to set effective_capabilities and/or `bounding_capabilities`, see the docs document for their semantics and interaction with the agent configuration, e.g., https://mesos.apache.org/documentation/latest/isolators/linux-capabilities/#task-setup. Most of the public Mesos APIs are defined in files under https://github.com/apache/mesos/tree/558829eb24f4ad636348497075bbc0428a4794a4/include/mesos, either in protobuf form or as C++ header files. For questions like yours it often helps to work backwards from an interesting field to a structure (e.g., in this particular case: work out how `CapabilityInfo` is related to `TaskInfo`). HTH, Benjamin
