- #Cloudera docker on mac how to
- #Cloudera docker on mac install
- #Cloudera docker on mac free
- #Cloudera docker on mac mac
Now you can start the saved container which will expose the Hue interface on localhost:8888.
Note An alternative way of using docker commit is to keep the hue.ini configuration file outside of the docker image and simply mount it inside when starting the container as shown in the Docker How-to. Now from another terminal use docker ps to identify the Hue container id and commit its state to remember the configuration even after stopping it: docker ps
#Cloudera docker on mac free
Note As a bonus, feel free to also add a MySql interpreter pointing to the Hue database, it can queries itself with no issues: ]]
#Cloudera docker on mac how to
If you don't have a running HiveServer2, check the development quickstart that demoes how to boot one quickly with (Docker too ): Then, we add the following block to the and sections so that we can query the Apache Hive instance running in one server we have access to. Note An alternative way to boot a production ready Hue with its own MySQL database is to use the Docker compose. If you don’t have an image locally, it will be downloaded and after that the container will be created. Host= # Use 127.0.0.1 and not localhost if on the same host (Run Cloudera QuickStart using Docker) sudo docker run -hostnamequickstart.cloudera -privilegedtrue -t -i -v /src:/src -publish-alltrue -p 8888 -p 7180 cloudera/quickstart /usr/bin/docker-quickstart Now please wait few seconds or minutes. Here we go with MySQL and fill-up the ] section with the credentials:
#Cloudera docker on mac install
Now let's open the configuration file: apt-get install -y vimįirst let's make sure that Hue is backed by a relational database supporting transactions like MySQL, PostgreSql or Oracle. This puts us into the /usr/share/hue home folder of the Hue installation. Let's pull and start the latest Hue container and open a shell inside it: docker run -it -p 8888:8888 gethue/hue:latest /bin/bash This one can be started or stopped or replicated multiple times depending on the load or high availability requirements.
#Cloudera docker on mac mac
This is out of the box config that works in Linux and not in MAC as I have mentioned earlier. But when I do a hbase master start the same thing happens that I have mentioned earlier.Īlthough it might not help, I forwarded the port 2181 on docker and changed domain to localhost in the site.xml (one of few ways I was trying and listed down all the things I tried) I am starting to think it's not zookeeper relatedĪlso, after hbase zookeeper start I can use hbase zkcli and get connected to zookeeper.
Stopped the zookeeper and let hbase manage it's own zookeeper - both cases hbase isnt' starting correctly due to which hbase client complains about zookeeper. I have tried both zookeeper as individual (outside hbase) - this works with kafka. 01:11:46,137 INFO zookeeper.ClientCnxn: Socket connection established to localhost/127.0.0.1:2181, initiating sessionĪfter this, master process waits for region server (count to settle), when I do a hbase regionserver start master gets killed (no reason specified), region server goes on to complain it cant report to master. Will not attempt to authenticate using SASL (unknown error) Kafka on the same docker can connect to zookeeper at port 2181 hbase master start -> says it connected to zookeeper 01:11:46,134 INFO zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2181. I have followed all the other links here checking the conf/*XML, on docker port forwarding, running zookeeper independently and let hbase manage zookeeper