Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
Labels (1)
avatar
Expert Contributor

If you have ever tried to spawn multiple cloudbreak shells you may have run into an error. That is because the default "cbd util cloudbreak-shell" uses docker containers. The fastest work around of this is to use the Jars directly. These Jars can be remotely run from your personal machine or run on the cloudbreak machine itself.

Prepping the cloudbreak machine(only needed if running jars locally on the AWS image)

  • Log into your cloudbreak instance and go to /etc/yum.repos.d
  • Remove the Centos-Base.repo file (this is a redhat machine and this can cause conflicts)
  • Install java-8 (yum install java-1.8.0*)
  • Change directory back to /home/cloudbreak

Downloading the Jar

Using the Jar

  • Interactive mode (java -jar ./cloudbreak-shell.jar --cloudbreak.address=https://<your-public-hostname> [email protected] --sequenceiq.password=cloudbreak --cert.validation=false)
  • Using a command file (java -jar ./cloudbreak-shell.jar --cloudbreak.address=https://<your-public-hostname> [email protected] --sequenceiq.password=cloudbreak --cert.validation=false --cmdfile=<your-FILE>)
1,368 Views
Version history
Last update:
‎01-17-2017 06:43 PM
Updated by:
Contributors