You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears though that there needs to be a little more work on the FreeBSD capabilities side so that it'll mount the Puppet paths via NFS.
Log
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'freebsd-9.2.amd64-puppet-coreitpro'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Fixed port collision for 22 => 2222. Now on port 2200.
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2200 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] Configuring and enabling network interfaces...
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
[default] Mounting NFS shared folders...
[default] Mounting shared folders...
[default] -- /tmp/vagrant-puppet-1/manifests
Vagrant attempted to execute the capability 'mount_virtualbox_shared_folder'
on the detect guest OS 'freebsd', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.
Vagrantfile
# -*- mode: ruby; -*-Vagrant.configure("2")do |config|
config.vm.guest=:freebsdconfig.vm.box_url="https://masakari.coreitpro.com/files/freebsd-9.2-amd64-puppet-coreitpro.box"config.vm.box="freebsd-9.2.amd64-puppet-coreitpro"config.vm.network"private_network",ip: "10.0.1.10"# Use NFS as a shared folderconfig.vm.synced_folder".","/vagrant",:nfs=>true,id: "vagrant-root"config.vm.provider:virtualboxdo |vb|
# vb.customize ["startvm", :id, "--type", "gui"]vb.customize["modifyvm",:id,"--memory","512"]vb.customize["modifyvm",:id,"--cpus","2"]vb.customize["modifyvm",:id,"--hwvirtex","on"]vb.customize["modifyvm",:id,"--audio","none"]vb.customize["modifyvm",:id,"--nictype1","virtio"]vb.customize["modifyvm",:id,"--nictype2","virtio"]endconfig.vm.provision:puppetdo |puppet|
puppet.module_path=["manifests","modules"]puppet.nfs=trueendend
The text was updated successfully, but these errors were encountered:
Currently FreeBSD has not implemented vboxsf support in their guest additions, so I was looking for a workaround for not being able to mount
vboxsf
filesystems, and stumbled across 3822d8e by @mfournier, which allows the usage of NFS for Puppet.It appears though that there needs to be a little more work on the FreeBSD capabilities side so that it'll mount the Puppet paths via NFS.
Log
Vagrantfile
The text was updated successfully, but these errors were encountered: