Hello,
Is anybody using CommandInfo::ContainerInfo protobuf message from Mesos 0.19? It was deprecated in Mesos 0.20 in favor of the top-level ContainerInfo message used as a field in TaskInfo/ExecutorInfo. As per MESOS-2315 <https://issues.apache.org/jira/browse/MESOS-2315> we’d like to remove CommandInfo::ContainerInfo. Please verify that you are using the correct ContainerInfo, and let us know if amu help needed to switch. Following is an example on how to use top level ContainerInfo, using DOCKER. The current supported options are Docker & Mesos and is designed so as it can be extended. ………….. TaskInfo task; task.set_name("Task " + lexical_cast<string>(taskId)); task.mutable_task_id()->set_value(lexical_cast<string>(taskId)); task.mutable_slave_id()->MergeFrom(offer.slave_id()); task.mutable_command()->set_value(“touch hello.txt”); ContainerInfo containerInfo; containerInfo.set_type(ContainerInfo::DOCKER); ContainerInfo::DockerInfo dockerInfo; dockerInfo.set_image("busybox"); containerInfo.mutable_docker()->CopyFrom(dockerInfo); task.mutable_container()->CopyFrom(containerInfo); ………………. For reference, an example on possible was CommandInfo::ContainerInfo, may be getting used, ………………. TaskInfo task; task.set_name("Task " + lexical_cast<string>(taskId)); task.mutable_task_id()->set_value(lexical_cast<string>(taskId)); task.mutable_slave_id()->MergeFrom(offer.slave_id CommandInfo command; CommandInfo::ContainerInfo containerInfo; containerInfo.set_image("docker:///busybox"); containerInfo.add_options("-v /tmp:/tmp"); command.set_value("echo hello"); command.mutable_container()->CopyFrom(containerInfo); task.mutable_command()->CopyFrom(command); …………………… If no objections are received within next *72* *hours*, we plan to move forward and remove the code. Thanks
