MicroPCF doesn't start without Internet connectivity about pcfdev

[sclevine]

Hi @debu66er,

If you start MicroPCF without internet access, the *.local.micropcf.io CNAME will not resolve. This prevents MicroPCF from booting. It's possible to shim out the CNAME with dnsmasq on the host. See here.

We have a story in our backlog to address the startup issue by introducing dnsmasq inside the VM.

[benlaplanche]

I successfully followed this guide on OSX https://passingcuriosity.com/2013/dnsmasq-dev-osx/

[MeiyappanKannappa]

Hi , I have same issue, But I have internet connectivity through proxy. I am able to download vagrant micropcf files through proxy but after that it hangs at**_ ==> default: Waiting for services to start..._** for long time. Can you help me. Many thanks!!!!

[wgorder]

+1 not proxy friendly. Everything fine up to waiting for services to start.

[jmcolyer]

+1 on the proxy sticking at "Waiting for services to start."

[jmcolyer]

@benlaplanche I tried to follow the guide that you mentioned, but it hangs on "Waiting for services to start...". If I put vagrant in UI mode, it brings up a login prompt at that point. Any suggestions?

[wgorder]

@sclevine What does the story around this look like?

We are looking at PCF for our enterprise. This looked promising for improving the dev experience with distributed cloud architectures however its seems impossible to get this to work behind our corporate proxies. I am not sure if I am missing a step or if that is a use case you do not plan on supporting.

Thanks,

[wgorder]

Nvm now I see @davidwadden posted a deprecation notice. Lattice- > micropcf -> PCF Dev... I am getting dizzy.

I will reach out to our account manager and get the closed beta I guess. I assume it has feature parity with what this offers..

[sclevine]

Hi @wgorder,

Happy to hear that you've found MicroPCF useful! We're working on an early customer access group for the PCF Dev closed beta on Pivnet. We also plan to resume our Github presence very soon. Unlike the product transition from Lattice to MicroPCF, the PCF Dev name change is more of a re-branding with a greater focus on providing PCF functionality locally.

The latest closed beta release of PCF Dev should start behind a proxy, and we have work in flight for more complete support.

Please let us know if you run into any other issues,
Stephen