You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2016/07/13 13:21:20 UTC
[jira] [Created] (MESOS-5840) Mesos claims an IP belongs to the
overlay network, even though it doesn't.
Gastón Kleiman created MESOS-5840:
-------------------------------------
Summary: Mesos claims an IP belongs to the overlay network, even though it doesn't.
Key: MESOS-5840
URL: https://issues.apache.org/jira/browse/MESOS-5840
Project: Mesos
Issue Type: Bug
Components: network
Reporter: Gastón Kleiman
Using DC/OS' IPAM module, we attempted to launch a Docker task using {{BRIDGE}} networking, while also requesting an IP in an overlay network through the {{NetworkInfo}} message.
The IP subnet for that overlay network is {{192.168.0.0/17}}, but the the IP in {{TaskStatus}} is the private Docker {{BRIDGE}} IP: {{172.17.0.3}}.
It is confusing/inconsistent that {{TaskStatus.NetworkInfo\[0\].name}} is still {{overlay-network}}, but the IP is not in the right subnet.
{code}
{
"id": "bridge.bfdf8491-48f6-11e6-abde-06f05fb76c9f",
"name": "bridge",
"slave_id": "09d73fd0-3413-4934-8657-be2a29f2361a-S0",
"state": "TASK_RUNNING",
[...]
"statuses": [
{
"state": "TASK_RUNNING",
"timestamp": 1468413530.91615,
"labels": [
{
"key": "Docker.NetworkSettings.IPAddress",
"value": "172.17.0.3"
}
],
"container_status": {
"network_infos": [
{
"labels": [],
"ip_addresses": [
{
"ip_address": "172.17.0.3" // this is the Docker Bridge interface private IP
}
],
"name": "overlay-network"
}
]
}
}
],
"container": {
"type": "DOCKER",
"docker": {
"image": "busybox",
"network": "BRIDGE",
"privileged": false,
"force_pull_image": false
},
"network_infos": [
{
"ip_addresses": [
{}
],
"name": "overlay-network",
"labels": {}
}
]
}
}
]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)