Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CEDB1759F for ; Mon, 25 May 2015 21:50:17 +0000 (UTC) Received: (qmail 81740 invoked by uid 500); 25 May 2015 21:50:17 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 81686 invoked by uid 500); 25 May 2015 21:50:17 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 81674 invoked by uid 99); 25 May 2015 21:50:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 May 2015 21:50:17 +0000 Date: Mon, 25 May 2015 21:50:17 +0000 (UTC) From: =?utf-8?Q?R=C3=A9my_SAISSY_=28JIRA=29?= To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12032) start-build-env.sh produces docker env with no hadoop sources on MacOS with WMWare Fusion MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12032?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14= 558545#comment-14558545 ]=20 R=C3=A9my SAISSY commented on HADOOP-12032: -------------------------------------- I've just found what is going on. This is a known bug with the docker-machine's vmwarefusion driver. Should b= e fixed in docker 1.7.0. https://github.com/docker/machine/issues/641 The workaround for now is to: - manually enable folder sharing on the VM (in vmware preferences) - docker-machine ssh dev (ssh on the VM) - manually mount the volumes mapped on the start-build-env.sh script: $sudo mount -o loop /mnt/hgfs/Users/USERNAME/.m2 /Users/USERNAME/.m2= =20 $sudo mount -o loop /mnt/hgfs/Users/USERNAME/PATH/TO/HADOOP/FOLDER /Us= ers/USERNAME/PATH/TO/HADOOP/FOLDER Then ./start-build-env.sh from another terminal should work and connect to = the container with the content of the hadoop folder. > start-build-env.sh produces docker env with no hadoop sources on MacOS wi= th WMWare Fusion > -------------------------------------------------------------------------= ---------------- > > Key: HADOOP-12032 > URL: https://issues.apache.org/jira/browse/HADOOP-12032 > Project: Hadoop Common > Issue Type: Bug > Components: build > Reporter: R=C3=A9my SAISSY > > On MacOSX, the start-build-env.sh script builds a docker build environmen= t but the hadoop directory is empty. > The hadoop_env_checks.sh script executes properly. > Steps to reproduce: > - Create a docker machine with Fusion backend:=20 > docker-machine create -d vmwarefusion --vmwarefusion-memory-size 12288 --= vmwarefusion-disk-size 40000 --vmwarefusion-boot2docker-url https://github.= com/cloudnativeapps/boot2docker/releases/download/v1.6.0-vmw/boot2docker-1.= 6.0-vmw.iso dev > - Load the docker env: > eval $(docker-machine env dev) > - Run the start-build-env.sh script > ./start-build-env.sh > The Hadoop directory is empty. > Not sure on which side is the issue. Sorry for the inconvenience if it is= not on the start-build-env.sh script side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)