Sorry I'm so busy recently.

Glad you find out the solution. ;)

We use ruby in docker-hadoop.sh to parse yaml file.

This should be in README as well. Thanks for finding it out!

2015-12-08 23:51 GMT+08:00 Carsten Maul <[email protected]>:

> I solved this issue. The problem: ruby was not installed :-( I misjudged
> this error…
>
> Kind regards
>
> Carsten
>
>
> Am 07.12.2015 um 14:29 schrieb Carsten Maul <[email protected]>:
>
> Hi,
>
> I´am trying to install a docker based Hadoop cluster with Bigtop 1.0.0
> using the provisioner on Debian 8.2
>
> I am getting the following fatal errors during the Install, which I need
> to resolve:
>
> ---------------------------------------------------------------------------------------------------------
> *"Provisioners will not be run since container doesn't support SSH."*
>
>
> There are also the following (I think) non-fatal errors:
> ---------------------------------------------------------------------
> 1) ./docker-hadoop.sh: Zeile 95: /usr/bin/../embedded/bin/ruby: Datei oder
> Verzeichnis nicht gefunden
>
> *2) Warning: The use of 'import' is deprecated at
> /bigtop-home/bigtop-deploy/puppet/manifests/site.pp:71*
>
> *3) **Error: [] is not a string.  It looks to be a Array at
> /etc/puppet/modules/apt/manifests/source.pp:22*
>
>
> My setup:
> -------------
> Debian 8.2 (Jessie) x64
> Docker version 1.9.1, build a34a1d5
> Vagrant 1.7.4
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Bigtop 1.0.0 release
>
> My vagrantconfig.yaml config:
> ---------------------------------------------
> docker:
>         memory_size: "2048"
>         image: "bigtop/deploy:debian-8"
>
> boot2docker:
>         memory_size: "2048"
>         number_cpus: "1"
>
> repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.0.0/debian/8/x86_64
> "
> distro: debian
> components: [hadoop, yarn]
> namenode_ui_port: "50070"
> yarn_ui_port: "8088"
> hbase_ui_port: "60010"
> enable_local_repo: false
> smoke_test_components: [mapreduce, pig]
> jdk: "java-1.7.0-openjdk-devel.x86_64“
>
>
>
> This is the output during provisioning, as you can see every container
> produces the Provisioner error about the unsupported SSH
>
> -------------------------------------------------------------------------------------------------------------------------------
> root@bigtop:# ./docker-hadoop.sh --create 3
> Bringing machine 'bigtop1' up with 'docker' provider...
> Bringing machine 'bigtop2' up with 'docker' provider...
> Bringing machine 'bigtop3' up with 'docker' provider...
> *==> bigtop1: Creating the container...*
>     bigtop1:   Name: vagrant-puppet-docker_bigtop1_1449489428
>     bigtop1:  Image: bigtop/deploy:debian-8
>     bigtop1: Volume: /opt/bigtop.1.0.0:/bigtop-home
>     bigtop1: Volume:
> /opt/bigtop.1.0.0/bigtop-deploy/vm/vagrant-puppet-docker:/vagrant
>     bigtop1:   Port: 50070:50070
>     bigtop1:   Port: 8088:8088
>     bigtop1:   Port: 60010:60010
>     bigtop1:
>     bigtop1: Container created: 8d17364e510e776a
> *==> bigtop1: Starting container...*
> *==> bigtop1: Provisioners will not be run since container doesn't support
> SSH.*
> *==> bigtop2: Creating the container...*
>     bigtop2:   Name: vagrant-puppet-docker_bigtop2_1449489739
>     bigtop2:  Image: bigtop/deploy:debian-8
>     bigtop2: Volume: /opt/bigtop.1.0.0:/bigtop-home
>     bigtop2: Volume:
> /opt/bigtop.1.0.0/bigtop-deploy/vm/vagrant-puppet-docker:/vagrant
>     bigtop2:
>     bigtop2: Container created: 2239d6669c64d967
> *==> bigtop2: Starting container...*
> *==> bigtop2: Provisioners will not be run since container doesn't support
> SSH.*
> *==> bigtop3: Creating the container...*
>     bigtop3:   Name: vagrant-puppet-docker_bigtop3_1449489740
>     bigtop3:  Image: bigtop/deploy:debian-8
>     bigtop3: Volume: /opt/bigtop.1.0.0:/bigtop-home
>     bigtop3: Volume:
> /opt/bigtop.1.0.0/bigtop-deploy/vm/vagrant-puppet-docker:/vagrant
>     bigtop3:
>     bigtop3: Container created: 48e1dd4f18419e2f
> *==> bigtop3: Starting container...*
> *==> bigtop3: Provisioners will not be run since container doesn't support
> SSH.*
>
>
>

Reply via email to