Skip to content
This repository has been archived by the owner on Dec 5, 2017. It is now read-only.

Multi-port container within a pod failed to get scheduled on any of the minions (mesos slaves) #118

Closed
sourav82 opened this issue Jan 8, 2015 · 0 comments

Comments

@sourav82
Copy link

sourav82 commented Jan 8, 2015

I was creating a container exposing 2 ports on 2 different host ports as below -
{
"id": "app",
"apiVersion": "v1beta1",
"kind": "ReplicationController",
"desiredState": {
"replicas": 2,
"replicaSelector": {"name": "app"},
"podTemplate": {
"desiredState": {
"manifest": {
"version": "v1beta1",
"id": "app",
"containers": [
{
"name": "app",
"image": "10.227.125.10:5000/app-kubernetes",
"ports": [
{
"containerPort": 80,
"hostPort": 21001
},
{
"containerPort": 389,
"hostPort": 21002
}
]
}
]
}
},
"labels": {"name": "app"}
}
},
"labels": {"name": "app"}
}
There are 2 mesos slaves and 1 mesos master. Both the slaves have neen started with port range 21000-24000. While creating the replication controller from above json, POD tasks are lost due to invalid resource port 21002.

From the log -
resources: ports():[21002-21002, 21002-21002]" slave_id:<value:"20150106-160618-176022282-5050-17958-S44" > timestamp:1.420712403061897e+09 9:0 10:14
E0108 15:50:03.064990 04618 scheduler.go:381] Task lost: 'task_id:<value:"e8a044a5-971f-11e4-ae31-984be16ce9ba" > state:TASK_LOST message:"Task uses invalid resources: ports(
):[21002-21002, 21002-21002]" slave_id:<value:"20150106-160618-176022282-5050-17958-S44" > timestamp:1.420712403061897e+09 9:0 10:14 '

If I start only one container on host port 21002 mapping to container port 80 or 389, it works properly. Could you please help here if it allows us using multiple container ports inside a single pod?

@jdef jdef closed this as completed in a64d081 Jan 8, 2015
jdef added a commit that referenced this issue Jan 8, 2015
jdef added a commit that referenced this issue Jan 8, 2015
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant