You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2016/02/29 21:03:18 UTC
[jira] [Created] (MESOS-4820) Need to set `EXPOSED` ports from
docker images into `ContainerConfig`
Avinash Sridharan created MESOS-4820:
----------------------------------------
Summary: Need to set `EXPOSED` ports from docker images into `ContainerConfig`
Key: MESOS-4820
URL: https://issues.apache.org/jira/browse/MESOS-4820
Project: Mesos
Issue Type: Task
Components: containerization
Reporter: Avinash Sridharan
Priority: Critical
Most docker images have an `EXPOSE` command associated with them. This tells the container run-time the TCP ports that the micro-service "wishes" to expose to the outside world.
With the `Unified containerizer` project since `MesosContainerizer` is going to natively support docker images it is imperative that the Mesos container run time have a mechanism to expose ports listed in a Docker image. The first step to achieve this is to extract this information from the `Docker` image and set in the `ContainerConfig` . The `ContainerConfig` can then be used to pass this information to any isolator (for e.g. `network/cni` isolator) that will install port forwarding rules to expose the desired ports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)