Tim Weidner

The issue has been resolved, some headers were missing to build, it was my fault! :) Thanks so much for this driver, i'm glad to use linux on my laptop...

Yes, your machine is most likely not powerful enough for the default configuration of HDFS + Spark on minidcos. You will need to reduce the resource usage of both packages...

It might very well be possible already with the right configuration(`--masters 0` in a new cluster, pointing to the old clusters masters with a `--extra-config`) but we haven't come around...

Does your custom genconf dir include an IP detect script which points to the eth1 instead of eth0? > Am 24.07.2019 um 20:57 schrieb sarathkumar : > > Docker network...

https://minidcos.readthedocs.io/en/latest/dcos-docker-cli.html#using-a-custom-docker-network You need to use the IP detect script presented here. > Am 24.07.2019 um 20:57 schrieb sarathkumar : > > Docker network created with custom network configs. > >...

Given your setup you may need to change the script to eth4 though. > Am 24.07.2019 um 20:57 schrieb sarathkumar : > > Docker network created with custom network configs....

I'm not aware of how dcos-launch is currently used in tests, that's why I was raising this issue. Since it's not a default setting to restrict cluster access I believe...

Corresponding JIRA issue: https://jira.mesosphere.com/browse/DCOS-28736

Sounds good, that mitigates the problem and still allows people to monitor their specific plan if required. I'm afraid I can't confirm the changes as the Bamboo deployment in question...