[
https://issues.apache.org/jira/browse/AMBARI-23102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thai Bui updated AMBARI-23102:
------------------------------
Summary: start-build-env.sh failed in MacOS due to mount volume permissions
(was: start-build-env.sh failed in macos due to mount volume permissions)
> start-build-env.sh failed in MacOS due to mount volume permissions
> ------------------------------------------------------------------
>
> Key: AMBARI-23102
> URL: https://issues.apache.org/jira/browse/AMBARI-23102
> Project: Ambari
> Issue Type: Bug
> Reporter: Thai Bui
> Priority: Minor
>
> Currently, start-build-env.sh doesn't work if the host OS is MacOS and the
> docker container is run as any user other than root. This is because the
> ~/.m2 is mounted as `root` user under the home directory of a docker user
> (such as jane.doe).
> For example:
> {noformat}
> centos6:~/src $ ls -lah ~/.m2/
> total 20K
> drwxr-xr-x 1 1000 ftp 238 Jan 22 16:32 .
> drwx------ 5 thai.bui games 4.0K Feb 27 19:53 ..
> drwxr-xr-x 1 1000 ftp 4.6K Feb 27 19:52 repository
> -rw-r--r-- 1 1000 ftp 3.0K Aug 8 2017 settings.old{noformat}
> This causes maven to fail because it can't write to the ~/.m2/repository. I'm
> adding an option to ./start-build-env.sh to run as root to fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
