Ambari uses Vagrant shared folder as base dir

I’m running an Ambari Agent in a Vagrant environment. Vagrant mounts a folder via NFS in /var/vagrant. If I check the mounts after Vagrant has booted the machine, I get the following:

/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
10.20.30.1:/Users/username/Workspace/vagrant-ambari on /var/vagrant type nfs (rw,vers=3,udp,addr=10.20.30.1)

The Ambari agent now seems to use /var/vagrant/ as its base directory for installing some of its services. E.g. it creates a folder /var/vagran/hadoop/falcon and then tries a chown in this directory which doesn’t work due to the NFS mount.

When I unmount the folder and then start the provisioning, everything works fine.

My question is: can I somehow prevent the agent from using this directory or configure which directory to use to put the service in?

Thx for any help!