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/04/06 06:10:25 UTC
[jira] [Created] (MESOS-5127) Reset `LIBPROCESS_IP` in
`network\cni` isolator.
Avinash Sridharan created MESOS-5127:
----------------------------------------
Summary: Reset `LIBPROCESS_IP` in `network\cni` isolator.
Key: MESOS-5127
URL: https://issues.apache.org/jira/browse/MESOS-5127
Project: Mesos
Issue Type: Bug
Components: containerization
Environment: Linux
Reporter: Avinash Sridharan
Assignee: Avinash Sridharan
Currently the `LIBPROCESS_IP` environment variable was being set to
the Agent IP if the environment variable has not be defined by the
`Framework`. For containers having their own IP address (as with
containers on CNI networks) this becomes a problem since the command
executor tries to bind to the `LIBPROCESS_IP` that does not exist in
its network namespace, and fails. Thus, for containers launched on CNI
networks the `LIBPROCESS_IP` should not be set, or rather is set to
"0.0.0.0", allowing the container to bind to the IP address provided
by the CNI network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)