Coder Social home page Coder Social logo

Comments (6)

davidwadden avatar davidwadden commented on July 19, 2024

we plan supporting running microPCF in an offline configuration at some point in the near future, but we haven't prioritized supporting that just yet. if you're interested in experimenting on your own, i think you may be able to run a version of dnsmasq on your host that handles this.

i'm curious where you get 8.8.8.8 from. i checked my /etc/resolv.conf running using VMware Fusion:

○ → vagrant ssh -c "cat /etc/resolv.conf"
nameserver 127.0.0.1
nameserver 172.16.139.2
search localdomain
Connection to 172.16.139.204 closed.

Which looks like after the consul DNS server, it goes to the host IP on the NAT interface (basically delegates to the Host to perform the DNS lookup). Is that where you have 8.8.8.8 configured as your DNS? This is where I think you could slip in DNSMasq as a custom resolver on the host to handle resolution for the local.micropcf.io subdomain.

from pcfdev.

dwu-pivotal avatar dwu-pivotal commented on July 19, 2024

Do you mean our script copy from the host's resolv.conf, and write to the vagrant VM? Let me have a try on this. thx

from pcfdev.

sclevine avatar sclevine commented on July 19, 2024

Doing that would break microPCF by preventing services inside of it from finding each other.

David is saying that *.local.micropcf.io needs to resolve to 192.168.11.11 on the host machine for microPCF to work properly. One way to accomplish this is by running dnsmasq on the host to create a wildcard CNAME record. See here.

from pcfdev.

dwu-pivotal avatar dwu-pivotal commented on July 19, 2024

Thx. But my /etc/resolv.conf in both vagrant vm, and app contriner is
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 10.0.2.2
How can I change that to point to my host dnsmasq?

from pcfdev.

sclevine avatar sclevine commented on July 19, 2024

10.0.2.2 is the host address, so your microPCF resolv.conf is already configured to query port 53 on the host. Running dnsmasq on port 53 with the configuration described above may just work.

from pcfdev.

dwu-pivotal avatar dwu-pivotal commented on July 19, 2024

Change my resolv.conf to (dnsmasq before 8.8.8.8)
nameserver 127.0.0.1
nameserver 8.8.8.8,
bring vagrant up, the result in vagrant vm become
nameserver 127.0.0.1
nameserver 10.0.2.2
nameserver 8.8.8.8

Perfect. Thx Stephen!

from pcfdev.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.