question Re: Installing kudu and kafka in cloudera quickstart vm docker image in Support Questions

question Re: Installing kudu and kafka in cloudera quickstart vm docker image in Support Questions https://community.cloudera.com/t5/Support-Questions/Installing-kudu-and-kafka-in-cloudera-quickstart-vm-docker/m-p/338595#M232866 <a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/96508">@BigDataAvengers</a> can you tell us a bit about why you're installing this six year old image? Does what you've already installed work with acceptable responsiveness? You didn't say: <UL> <LI>where you retrieved the docker quickstart image from</LI> <LI>how much RAM your mac m1 has available</LI> <LI>whether or not you were actually able to successfully start up the services, beginning with the Cloudera Manager user interface, that were already present in the cloudera quickstart vm image you installed</LI> </UL> The docker image you've installed appears to be based on CDH 5.7, which went out of support at the end of August in 2019 and is even older than the most recent version of the CDH Quickstart, which was based on CDH 5.13, which itself is already out of support. Cloudera Enterprise 5.13 <A href="https://www.cloudera.com/legal/policies/support-lifecycle-policy.html" target="_blank" rel="noopener">reached it's end of support date in October 2020</A> (open that link and then expand the section labeled "Cloudera Enterprise products" underneath Current End of Support (EoS) Dates). For this reason, <A href="https://community.cloudera.com/t5/Support-Questions/Cloudera-QuickStart-VM-Download/m-p/290587/highlight/true#M214963" target="_blank" rel="noopener">Cloudera is no longer distributing the CDH 5-based Quickstart</A>. It is also why this hyperlink: <A href="http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cloudera_quickstart_vm.html" target="_blank">http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cloudera_quickstart_vm.html</A> …to the appropriate documentation results in an HTTP 404 error. And <A href="https://community.cloudera.com/t5/Support-Questions/Does-Quickstart-VM-CDH-5-13-has-Kafka/m-p/69543/highlight/true#M3633" target="_blank" rel="noopener">Kafka was never bundled and delivered with the cloudera quickstart</A>; it always required a separate installation.   Next, it's not at all certain that your M1 Mac has enough RAM available in total to be able to run the services you are attempting to run within the container (or containers) without consuming so much of the host machine's memory that OS X starts killing processes to free up memory, and Docker is very much one of the processes subject to being killed. IIRC the memory recommendation for the Docker version of the Quickstart VM itself was about 10 GB, so on a 16GB Mac, with the overhead for Docker and other running applications (such as a web browser), things will be running pretty tight as far as memory goes. Even if you were able to install the docker image that <a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/42173">@ckumar</a> pointed you to in another container alongside the quickstart's container, that does not mean that it would provide a useable system, because the HDF NiFi container called for at least 8 GB.   So while it is possible that someone with the requisite knowledge of the Linux command line and Docker combined with sufficient skill and abilities with the various required development tools could update the last, outdated cloudera quickstart image to add Kudu and then subsequently figure out how to run it alongside containers for some version of NiFi and Kafka (and indeed, some member of the Cloudera Community may have already done so and be willing to share their method in response to your question), it doesn't mean you'd have the necessary hardware resources to run it on your M1 Mac, or that it would produce acceptable results.   You should ask yourself whether or not this would be worthwhile.   The current Enterprise Data Platform offered by Cloudera as of this writing is Cloudera Data Platform (CDP), which in it's on-premises "form factor" is now called <A href="https://www.cloudera.com/products/cloudera-data-platform/cdp-private-cloud.html" target="_self">CDP Private Cloud</A>. CDP supersedes CDH and the components are at the appropriate versions that enable them to work together.   If you're just looking to evaluate a data platform, you can currently do so without a Cloudera subscription by downloading and installing <A href="https://www.cloudera.com/downloads/cdp-private-cloud-trial.html.html" target="_blank" rel="noopener">the Trial Version of CDP Private Cloud Base Edition</A> of Cloudera Data Platform. Cloudera has an extensive <A href="https://www.cloudera.com/tutorials/how-to-create-a-cdp-private-cloud-base-development-cluster.html/?utm_source=mktg-tutorial" target="_blank" rel="noopener">tutorial on installing CDP Private Cloud Base</A> in an Infrastructure as a service (IaaS) fashion using AWS on its website. This approach allows you to leverage machines which have hardware resources, such as plentiful RAM, that your laptop might not have available. And CDP Private Cloud Base Edition <A href="https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/runtime-release-notes/topics/rt-pvc-runtime-component-versions.html" target="_blank" rel="noopener">ships with Kudu</A>.     Mon, 14 Mar 2022 18:30:34 GMT ask_bill_brooks 2022-03-14T18:30:34Z