You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 5, 2017. It is now read-only.
user reported port conflict on a slave node because etcd_proxy was consuming a port that hadn't been properly allocated:
E0217 13:27:18.112458 6688 manager.go:1864] Failed to create pod infra container: API error (500): Cannot start container 4c74ded9de8418510f0c7966faef1a5adc834029b3e35829744bdcf6ee783a47: failed to create endpoint k8s_POD.e67a4f09_pod-38_default_50f9670b-d5a3-11e5-8fb3-005056ad6f59_e60cef0d on network bridge: Bind for 0.0.0.0:1052 failed: port is already allocated
The text was updated successfully, but these errors were encountered:
etcd-mesos isn't properly allocating a driver port from the resource pool
the etcd proxy running in the k8sm uber container is using local port 4001, not properly allocating that from the resource pool; since the container uses HOST networking mode this could create conflicts
going to change the k8s/dcos scheduler docker container to run in BRIDGE mode, requires some changes in the scheduler driver setup so that the correct IP is published to mesos, namely advertising an IP that matches that of LIBPROCESS_IP (if present)
user reported port conflict on a slave node because etcd_proxy was consuming a port that hadn't been properly allocated:
The text was updated successfully, but these errors were encountered: