Closed randyzwitch closed 8 years ago
Yeah, that's a known (and not easily fixable) limitation of using containers for networking. Basically, if you run a browser inside the container, links will work great because you'll have access to container-internal IP addresses and hostnames, but otherwise you're in trouble since Docker intentionally needs to isolate the networking stack within the container from the one on your host. One workaround is to open up a SOCKS 5 proxy to the host running Docker and having your browser use that for DNS resolution. That works fine on Linux hosts, but I've never tried it with Docker for Mac.
That's unfortunate for OSX users, but I guess it's not really an issue for you to solve. Guess I'm off to learn more about Docker.
Thanks!
Continuation of #6 I guess :)
On OSX, once Cloudera Manager is accessed, all of the Web UI links are broken. For example, going to Hue within CM:
The configuration thinks the URL should be
http://node-1.testing:8888/
, but I get a DNS errorSame thing with Oozie (
http://node-1.testing:11000/oozie
), Impala (http://node-1.testing:25020/
), etc