[
https://issues.apache.org/jira/browse/BIGTOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evans Ye updated BIGTOP-1167:
-----------------------------
Description:
By default, vagrant shell provisioner run shell scripts with superuser
privileges. Since provision.sh do hdfs write operations by root, it get
permission denied.
There're two ways we can fix it.
1). Create vagrant's home folder by hdfs.
2). Let vagrant shell provisioner run the shell script without superuser
privileges. (set privileged to false in Vagrantfile)
It seems solution 2 is much more elegant.
Unfortunately, the privileged setting is only available with vagrant 1.3.0+,
and there's another issue coming up with 1.3.5+ which [failed the network
setting in fedora|https://github.com/mitchellh/vagrant/issues/2430]. So, I
might suggest to take solution 1 fist.
was:
By default, vagrant shell provisioner run shell scripts with superuser
privileges. Since provision.sh do hdfs write operations by root, it get
permission denied.
There're two ways we can fix it.
1). Create vagrant's home folder by hdfs.
2). Let vagrant shell provisioner run the shell script without superuser
privileges. (set privileged to false in Vagrantfile)
It seems solution 2 is much more elegant.
Unfortunately, the privileged setting is only available with vagrant 1.30+, and
there's another issue coming up with 1.35+ which failed the network setting in
fedora. So, I might suggest to take solution 1 fist.
> got "Permission denied" when creating vagrant home folder in provision.sh
> -------------------------------------------------------------------------
>
> Key: BIGTOP-1167
> URL: https://issues.apache.org/jira/browse/BIGTOP-1167
> Project: Bigtop
> Issue Type: Bug
> Components: Deployment, VM
> Environment: vagrant 1.2.7,1.4.1
> Reporter: Evans Ye
> Priority: Minor
> Attachments: BIGTOP-1167.1.patch, BIGTOP-1167.2.patch
>
>
> By default, vagrant shell provisioner run shell scripts with superuser
> privileges. Since provision.sh do hdfs write operations by root, it get
> permission denied.
> There're two ways we can fix it.
> 1). Create vagrant's home folder by hdfs.
> 2). Let vagrant shell provisioner run the shell script without superuser
> privileges. (set privileged to false in Vagrantfile)
> It seems solution 2 is much more elegant.
> Unfortunately, the privileged setting is only available with vagrant 1.3.0+,
> and there's another issue coming up with 1.3.5+ which [failed the network
> setting in fedora|https://github.com/mitchellh/vagrant/issues/2430]. So, I
> might suggest to take solution 1 fist.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
