[
https://issues.apache.org/jira/browse/HADOOP-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558545#comment-14558545
]
Rémy 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 be
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
$sudo mount -o loop /mnt/hgfs/Users/USERNAME/PATH/TO/HADOOP/FOLDER
/Users/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 with
> WMWare Fusion
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-12032
> URL: https://issues.apache.org/jira/browse/HADOOP-12032
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Rémy SAISSY
>
> On MacOSX, the start-build-env.sh script builds a docker build environment
> but the hadoop directory is empty.
> The hadoop_env_checks.sh script executes properly.
> Steps to reproduce:
> - Create a docker machine with Fusion backend:
> 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)
