you are correct, I'm running this on Mac 10.10.5 On Sun, May 1, 2016 at 10:57 AM, Olaf Flebbe <o...@oflebbe.de> wrote:
> Hi, > > On what OS did you run ./docker-hadoop.sh ? Using Docker Quickstart sounds > like you are using this in MacOSX? > > I am using this on Linux on bare metal or on a virtualised host running > Linux. (More precisely on VMware Workstation/Fusion on Debian) > I am not sure if the boot2docker config actually works. > > Olaf > > > > Am 01.05.2016 um 16:18 schrieb Artem Ervits <artemerv...@gmail.com>: > > > > Cos, thanks for looking into this > > > > here are my steps, I opened a Docker Quickstart Terminal and within it a > screen session, result is the same without screen: > > > > bash-3.2$ docker pull bigtop/deploy:centos-6 > > centos-6: Pulling from bigtop/deploy > > > > a3ed95caeb02: Pull complete > > a2086e9272f4: Pull complete > > 26a11a230db8: Pull complete > > 44868e80d4a1: Pull complete > > 98592265a9d0: Pull complete > > 216fcbadde6d: Pull complete > > fdb163b8c866: Pull complete > > c6ec2cfce856: Pull complete > > Digest: > sha256:97ee16dc4fd1567d47840b2bc52d42c9c9689eb66a80d3c85e9a3c5c83ffb60f > > Status: Downloaded newer image for bigtop/deploy:centos-6 > > bash-3.2$ ./docker-hadoop.sh --create 3 > > The VirtualBox VM was created with a user that doesn't match the > > current user running Vagrant. VirtualBox requires that the same user > > be used to manage the VM that was created. Please re-run Vagrant with > > that user. This is not a Vagrant issue. > > > > The UID used to create the VM was: 0 > > Your UID is: 501 > > Docker container(s) startup failed! > > > > I then deleted config.rb and .vagrant files/directories and went back to > the original issue which was > > > > Docker command executed by Vagrant didn't complete successfully! > > The command run along with the output from the command is shown > > below. > > > > Command: "docker" "run" "--name" > "vagrant-puppet-docker_bigtop1_1462112094" "-d" "-p" "50070:50070" "-p" > "8088:8088" "-p" "60010:60010" "-v" > "/var/lib/docker/docker_1462112041_73828:/bigtop-home" "-v" > "/var/lib/docker/docker_1462112041_72214:/vagrant" "-h" "bigtop1.docker" > "--privileged=true" "-m" "2048m" "bigtop/deploy:centos-6" > > > > Stderr: Unable to find image 'bigtop/deploy:centos-6' locally > > Pulling repository bigtop/deploy > > time="2016-05-01T14:14:53Z" level="fatal" msg="Could not reach any > registry endpoint" > > > > Stdout: ESC[0m > > Docker container(s) startup failed! > > > > I do have the image loaded as you can see I pulled them from dockerhub > and here's the output of docker images > > > > vagrant-puppet-docker aervits$ docker images > > REPOSITORY TAG IMAGE ID CREATED > SIZE > > bigtop/deploy centos-6 cd58da899eb7 3 months > ago 399 MB > > > > > > On Sat, Apr 30, 2016 at 8:36 PM, Konstantin Boudnik <c...@apache.org> > wrote: > > Looks like a local configuration issue of some sort. Could you tell more > about > > your environment, perhaps post the steps and error message you're > getting? > > > > Thanks, > > Cos > > > > On Sat, Apr 30, 2016 at 04:32PM, Artem Ervits wrote: > > > I'm running the procedure in README for 1.1.0. Having issues with > deploying > > > a cluster. Complains that user launching the docker VM is not the same > as > > > running deployment. Does anyone have steps that do work? I also tried > with > > > 1.0 and was not successful. > > > >
