gael-ian / vagrant-bindfs Goto Github PK
View Code? Open in Web Editor NEWA Vagrant plugin to automate bindfs mount in the VM
License: MIT License
A Vagrant plugin to automate bindfs mount in the VM
License: MIT License
I have a Vagrant box (running Debian Wheezy) with vagrant-bindfs on an Ubuntu host. Here's a curious issue I'm experiencing:
vagrant@twx:/www/twx/logs$ ls -la debug.log
-rw-r--r-- 1 vagrant vagrant 77941 May 27 13:15 debug.log
vagrant@twx:/www/twx/logs$ chmod a+w debug.log
vagrant@twx:/www/twx/logs$ ls -la debug.log
-rw-r--r-- 1 vagrant vagrant 77941 May 27 13:15 debug.log
The chmod seems to have no effect at all. However, on the host filesystem the file now has 666 permissions!
I can change permissions of files outside the synced folder (eg. in /tmp) just fine. Any ideas?
I ran the command vagrant plugin install vagrant-bindfs in my terminal and got the following error:
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing vagrant-bindfs (0.4.12), and Bundler cannot continue.
Make sure that `gem install vagrant-bindfs -v '0.4.12'` succeeds before bundling.
Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::InstallError: vagrant-bindfs requires Ruby version ~> 2.0.0.
After that, I ran the command in the error: gem install vagrant-bindfs -v '0.4.12' and got this error:
ERROR: Error installing vagrant-bindfs:
vagrant-bindfs requires Ruby version ~> 2.0.0.
I used ruby -v and it said ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin14]
It seems that I have a version of Ruby that is higher than what it's asking for. What should I do to fix this?
Hi,
since I upgraded to vagrant 1.4 I get the following error with the vagrant-binfs plugin installed.
Bringing machine 'projectname' up with 'virtualbox' provider...
/Users/username/.vagrant.d/gems/gems/vagrant-bindfs-0.2.2/lib/vagrant-bindfs/plugin.rb:28:in `block (2 levels) in <class:Plugin>': uninitialized constant Vagrant::Action::Builtin::NFS (NameError)
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:45:in `call'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:45:in `block (2 levels) in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:44:in `tap'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:44:in `block in run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:43:in `map'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/action/runner.rb:43:in `run'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/machine.rb:147:in `action'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.0/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'
Hi, I was wondering if there is an option to sync a folder, but ignore certain files such as .vagrant
and node_modules
dir
I originally opened this on the composer/installers repo, but turns out it's something happening in bindfs. I have no idea exactly as I don't know where/how to get log files for bindfs errors. When using bindfs version 1.13.2 on the guest machine (redhat variety linux) I ran into an issue where composer/installers would simply fail to install. I realized it would work when the vagrant-bindfs plugin wasn't active, so I took a shot at simply upgrading the bind version to from 1.13.2 to 1.13.4 and lo-and-behold it works now. I'm happy to try and debug more if you want. You can see the composer output on the other issue if interested. If not, it might be a good idea to bump the bindfs version installed on redhat machines (when installed from source).
Hello there.
I have some wired error and Google not help with solution :(
$ vagrant plugin list
vagrant-bindfs (0.4.11)
vagrant-hostmanager (1.8.5)
vagrant-share (1.1.5, system)
vagrant-vmware-fusion (4.0.14)
$ vagrant -v
Vagrant 1.8.7
So when i run $ vagrant up/reload --debug
it says:
...
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:189:in `<main>'
INFO interface: error: The bind command `bindfs --force-user=vagrant --force-group=vagrant --perms=u=rwX:g=rD:o=rD /vagrant-nfs /vagrant/httpdocs` failed to run!
Please check options values and compatibility. For a complete documentation,
run `sudo bindfs --help` on the VM.
You can see it online at http://bindfs.org/docs/bindfs.1.html
The bind command `bindfs --force-user=vagrant --force-group=vagrant --perms=u=rwX:g=rD:o=rD /vagrant-nfs /vagrant/httpdocs` failed to run!
Please check options values and compatibility. For a complete documentation,
run `sudo bindfs --help` on the VM.
You can see it online at http://bindfs.org/docs/bindfs.1.html
Can you tell me please how to fix it?
Thanks
Versions 0.4.10 and 0.4.11 can only be installed in Vagrant > 1.7.4?
% vagrant --version
Vagrant 1.7.4
% vagrant plugin install vagrant-bindfs
Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing vagrant-bindfs (0.4.11), and Bundler cannot continue.
Make sure that `gem install vagrant-bindfs -v '0.4.11'` succeeds before bundling.
Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::InstallError: vagrant-bindfs requires Ruby version ~> 2.2.
% vagrant plugin install vagrant-bindfs --plugin-version 0.4.10
Installing the 'vagrant-bindfs --version '0.4.10'' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing vagrant-bindfs (0.4.10), and Bundler cannot continue.
Make sure that `gem install vagrant-bindfs -v '0.4.10'` succeeds before bundling.
Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::InstallError: vagrant-bindfs requires Ruby version ~> 2.2.
% vagrant plugin install vagrant-bindfs --plugin-version 0.4.9
Installing the 'vagrant-bindfs --version '0.4.9'' plugin. This can take a few minutes...
Installed the plugin 'vagrant-bindfs (0.4.9)'!
I can't get the bindfs plugin working with a OSX guest based on the jhcook/osx-elcapitan-10.11
box from HashiCorp.
I have configured the NFS and the bindfs as follows:
config.vm.synced_folder ".", "/vagrant-nfs", type: "nfs", mount_options: ['rw', 'vers=3', 'udp', 'actimeo=2', 'resvport', 'fsc', 'nolock', 'noatime']
config.bindfs.bind_folder "/vagrant-nfs", "/vagrant", after: :provision
Above works great on all systems as long as the guest OS isn't OSX. I also tried and installed brew cask install osxfuse
and brew install homebrew/fuse/bindfs
on the guest, but even then I get the same error. What can I do to get bindfs working in this setup?
Vagrant attempted to execute the capability 'bindfs_installed'
on the detect guest OS 'darwin', 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.
Basically I am now in stuck to share /var/lib/mysql/
.
So I am sharing the /var/lib/mysql
folder in ./mysql
.
Original config.vm.synced_folder "./mysql", "/var/lib/mysql", type: "nfs"
was working fine except the permission errors. So I have chosen your plugin but unfortunately I could not make it work; the folder is not syncing. Seems to be that I am missing something. Can you please guide me? I am using OSX Yosemite.
And the server is ubuntu/trusty64.
config.vm.box = "ubuntu/trusty64"
#syncing nicely
config.vm.synced_folder "./www", "/var/www", type: "nfs"
config.vm.synced_folder "./apache2/etc", "/etc/apache2", type: "nfs"
config.vm.synced_folder "./apache2/log", "/var/log/apache2", type: "nfs"
config.vm.synced_folder "./apache2/php5", "/etc/php5/apache2", type: "nfs"
###config.vm.synced_folder "./mysql", "/var/lib/mysql", type: "nfs"
#Not syncing
config.bindfs.bind_folder "/var/lib/mysql", "./mysql", after: :provision
sudo apt-get install mysql-server php5-mysql -y
sudo mysql_install_db
#tried with this also not working
sudo chattr -ia -R /var/lib/mysql
sudo chmod -R 755 /var/lib/mysql/
using nfs fails, default works.
macOS Sierra 10.12.1
VirtualBox 5.1.10
Vagrant 1.9.1
Virtualbox Guest Additions 5.1.10
plugins...
vagrant-bindfs 1.0.2
vagrant-vbguest 0.13.0
ERROR
==> machine1: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp 192.168.56.1:/Users/cpeterson/PhpstormProjects /mnt/vagrant-vflsf_wvwgarzn1wd6
result=$?
if test $result -eq 0; then
if test -x /sbin/initctl && command -v /sbin/init && /sbin/init 2>/dev/null --version | grep upstart; then
/sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=/mnt/vagrant-vflsf_wvwgarzn1wd6
fi
else
exit $result
fi
Stdout from the command:
Stderr from the command:
mount.nfs: access denied by server while mounting 192.168.56.1:/Users/cpeterson/PhpstormProjects
config.yaml
vagrantfile:
target: local
vm:
provider:
local:
box: puphpet/centos7-x64
box_url: puphpet/centos7-x64
box_version: '0'
chosen_virtualizer: virtualbox
virtualizers:
virtualbox:
modifyvm:
natdnshostresolver1: false
showgui: 0
vmware:
numvcpus: 1
parallels:
linked_clone: 0
check_guest_tools: 0
update_guest_tools: 0
machines:
vflm_kkeu720e4g60:
id: machine1
hostname: machine1.puphpet
network:
private_network: 192.168.56.199
forwarded_port:
vflmnfp_kc6yb7mx0zjq:
host: '7951'
guest: '22'
memory: '512'
cpus: '1'
provision:
puppet:
manifests_path: puphpet/puppet/manifests
module_path:
- puphpet/puppet/modules
- puphpet/puppet/manifests
options:
- '--verbose'
- '--hiera_config /vagrant/puphpet/puppet/hiera.yaml'
synced_folder:
vflsf_wvwgarzn1wd6:
source: ~/PhpstormProjects
target: /var/www/vhosts
sync_type: nfs
smb:
smb_host: ''
smb_username: ''
smb_password: ''
mount_options:
dir_mode: '0775'
file_mode: '0664'
rsync:
args:
- '--verbose'
- '--archive'
- '-z'
exclude:
- .vagrant/
- .git/
auto: 'true'
owner: www-data
group: www-data
usable_port_range:
start: 10200
stop: 10500
post_up_message: ''
ssh:
host: 'false'
port: 'false'
private_key_path: 'false'
username: vagrant
guest_port: 'false'
keep_alive: '1'
forward_agent: 'false'
forward_x11: 'false'
shell: 'bash -l'
insert_key: 'false'
vagrant:
host: detect
proxy:
http: ''
https: ''
ftp: ''
no_proxy: ''
server:
install: '1'
packages: { }
users_groups:
install: '1'
groups: { }
users: { }
locale:
install: '1'
settings:
default_locale: en_US.UTF-8
locales:
- en_GB.UTF-8
- en_US.UTF-8
timezone: UTC
firewall:
install: '1'
rules: { }
cron:
install: '1'
jobs: { }
nginx:
install: '0'
settings:
version: present
default_vhost: 1
proxy_buffers: '4 256k'
proxy_buffer_size: 128k
proxy_connect_timeout: 600s
proxy_send_timeout: 600s
proxy_read_timeout: 600s
names_hash_bucket_size: 128
upstreams: { }
vhosts:
nxv_ldraisbqs1qn:
server_name: awesome.dev
server_aliases:
- www.awesome.dev
www_root: /var/www/awesome
listen_port: '80'
client_max_body_size: 1m
ssl: '0'
ssl_cert: ''
ssl_key: ''
ssl_port: '443'
ssl_protocols: ''
ssl_ciphers: ''
rewrite_to_https: '1'
spdy: '1'
locations:
nxvl_rpdx37bzzorj:
www_root: ''
location: /
index_files:
- index.html
- index.htm
- index.php
try_files:
- $uri
- $uri/
- /index.php$is_args$args
fastcgi: ''
fastcgi_index: ''
fastcgi_split_path: ''
proxy: ''
proxy_redirect: ''
nxvl_7nkhjozjr9du:
www_root: ''
location: '~ \.php$'
try_files:
- $uri
- $uri/
- /index.php$is_args$args
fastcgi: '127.0.0.1:9000'
fastcgi_index: index.php
fastcgi_split_path: '^(.+\.php)(/.*)$'
fast_cgi_params_extra:
- 'SCRIPT_FILENAME $request_filename'
- 'APP_ENV dev'
set:
- '$path_info $fastcgi_path_info'
proxy: ''
proxy_redirect: ''
proxies: { }
apache:
install: '1'
settings:
version: 2.4
user: www-data
group: www-data
default_vhost: true
manage_user: false
manage_group: false
sendfile: 0
modules:
- proxy_fcgi
- rewrite
vhosts:
av_oaq3ccdmlp21:
servername: awesome.dev
serveraliases:
- www.awesome.dev
docroot: /var/www/vhosts/dev
port: '80'
setenv:
- 'APP_ENV dev'
setenvif:
- 'Authorization "(.*)" HTTP_AUTHORIZATION=$1'
custom_fragment: ''
ssl: '0'
ssl_cert: ''
ssl_key: ''
ssl_chain: ''
ssl_certs_dir: ''
ssl_protocol: ''
ssl_cipher: ''
directories:
avd_vnpgoxm51cx4:
path: /var/www/vhosts/dev
options:
- Indexes
- FollowSymlinks
- MultiViews
allow_override:
- All
require:
- 'all granted'
custom_fragment: ''
files_match:
avdfm_wmge9rcasi7k:
path: \.php$
sethandler: 'proxy:fcgi://127.0.0.1:9000'
custom_fragment: ''
provider: filesmatch
provider: directory
letsencrypt:
install: '1'
settings:
email: ''
domains: { }
php:
install: '1'
settings:
version: '7.0'
modules:
php:
- cli
- intl
- xml
pear: { }
pecl: { }
ini:
display_errors: 'On'
error_reporting: '-1'
session.save_path: /var/lib/php/session
date.timezone: UTC
fpm_ini:
error_log: /var/log/php-fpm.log
fpm_pools:
phpfp_yfy57q7qfh22:
ini:
prefix: www
listen: '127.0.0.1:9000'
security.limit_extensions: .php
user: www-user
group: www-data
composer: '1'
composer_home: ''
xdebug:
install: '1'
settings:
xdebug.default_enable: '1'
xdebug.remote_autostart: '0'
xdebug.remote_connect_back: '1'
xdebug.remote_enable: '1'
xdebug.remote_handler: dbgp
xdebug.remote_port: '9000'
blackfire:
install: '0'
settings:
server_id: ''
server_token: ''
agent:
http_proxy: ''
https_proxy: ''
log_file: stderr
log_level: '1'
php:
agent_timeout: '0.25'
log_file: ''
log_level: '1'
xhprof:
install: '0'
wpcli:
install: '0'
version: v0.24.1
drush:
install: '0'
version: 8.0.5
ruby:
install: '1'
versions:
rv_e4ual7ij3i7k:
default: '1'
bundler: '1'
version: 2.3.1
gems:
- [email protected]
- [email protected]
- [email protected]
python:
install: '1'
packages: { }
versions: { }
nodejs:
install: '0'
settings:
version: '6'
npm_packages: { }
hhvm:
install: '0'
composer: '1'
composer_home: ''
settings: { }
server_ini:
hhvm.server.host: 127.0.0.1
hhvm.server.port: '9000'
hhvm.log.use_log_file: '1'
hhvm.log.file: /var/log/hhvm/error.log
php_ini:
display_errors: 'On'
error_reporting: '-1'
date.timezone: UTC
mariadb:
install: '1'
settings:
version: '10.1'
root_password: '123'
override_options: { }
adminer: 0
users:
mariadbnu_gyzqdlofynmr:
name: dbuser
password: '123'
databases:
mariadbnd_ctcvlouw2p29:
name: dbname
sql: ''
grants:
mariadbng_zjyfd2nvjzbs:
user: dbuser
table: '*.*'
privileges:
- ALL
mysql:
install: '0'
settings:
version: '5.7'
root_password: '123'
override_options: { }
adminer: 0
users:
mysqlnu_rvi8axh9ruiw:
name: dbuser
password: '123'
databases:
mysqlnd_gftgskol807c:
name: dbname
sql: ''
grants:
mysqlng_i5g2cqaf2t3f:
user: dbuser
table: '*.*'
privileges:
- ALL
postgresql:
install: '0'
settings:
global:
encoding: UTF8
version: '9.6'
server:
postgres_password: '123'
databases: { }
users: { }
grants: { }
adminer: 0
mongodb:
install: '0'
settings:
bind_ip: 127.0.0.1
port: '27017'
globals:
version: 2.6.0
databases: { }
redis:
install: '0'
settings:
port: '6379'
sqlite:
install: '0'
adminer: 0
databases: { }
mailhog:
install: '0'
settings:
smtp_ip: 0.0.0.0
smtp_port: 1025
http_ip: 0.0.0.0
http_port: '8025'
path: /usr/local/bin/mailhog
beanstalkd:
install: '0'
settings:
listenaddress: 0.0.0.0
listenport: '11300'
maxjobsize: '65535'
maxconnections: '1024'
binlogdir: /var/lib/beanstalkd/binlog
binlogfsync: null
binlogsize: '10485760'
beanstalk_console: 0
rabbitmq:
install: '0'
settings:
port: '5672'
users: { }
vhosts: { }
plugins: { }
elastic_search:
install: '0'
settings:
version: 2.3.1
java_install: true
instances:
esi_0ut5i7ylbubf:
name: es-01
solr:
install: '0'
settings:
version: 5.5.2
port: '8984'
Yosemite 10.10.1
ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]
gem 2.0.14
Vagrant 1.7.2
rming@rmingwang:~/vagrant/work$ vagrant plugin install vagrant-bindfs
Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing rdoc (4.2.0), and Bundler cannot continue.
Make sure that `gem install rdoc -v '4.2.0'` succeeds before bundling.
NoMethodError: undefined method `size' for nil:NilClass
rming@rmingwang:~/vagrant/work$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.0)
CFPropertyList (2.2.8)
io-console (0.4.2)
json (1.7.7)
libxml-ruby (2.6.0)
minitest (4.3.2)
nokogiri (1.5.6)
psych (2.0.0)
rake (0.9.6)
rdoc (4.2.0, 4.0.0)
sqlite3 (1.3.7)
test-unit (2.0.0.0)
vagrant-bindfs (0.3.2)
What is the syntax for disabling an option? Ex. you have force-user
set to "vagrant" by default. How do I disable force-user
altogether? I tried:
config.bindfs.bind_folder "/var/www_tmp", "/var/www", force_user: nil, mirror: "@sysadmin", chown_ignore: true, chgrp_ignore: true, chmod_ignore: true, chmod_allow_x: true
but that just threw a bunch of ruby errors when it tried to mount.
How can this be achieved ?
app
and want to mount /vagrant
into /home/app/runtime
Getting this error when trying to install this. Tried to install nokogiri on my own and found errors pointing me to this http://stackoverflow.com/questions/22703393/clang-error-unknown-argument-mno-fused-madd-wunused-command-line-argumen
So got nokogiri installed, but when trying to install again it still throws me this..
Trying to install on osx and getting this error
Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:An error occurred while installing ffi (1.9.14), and Bundler cannot continue.
Make sure thatgem install ffi -v '1.9.14'
succeeds before bundling.Warning: this Gemfile contains multiple primary sources. Using
source
more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, runbundle config disable_multisource true
.Gem::Ext::BuildError: ERROR: Failed to build gem native extension./opt/vagrant/embedded/bin/ruby -r ./siteconf20160721-10219-1pot6r1.rb extconf.rb
checking for ffi.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.Provided configuration options:
'
--with-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/opt/vagrant/embedded/bin/$(RUBY_BASE_NAME)
--with-ffi_c-dir
--without-ffi_c-dir
--with-ffi_c-include
--without-ffi_c-include=${ffi_c-dir}/include
--with-ffi_c-lib
--without-ffi_c-lib=${ffi_c-dir}/lib
--with-libffi-config
--without-libffi-config
--with-pkg-config
--without-pkg-config
/opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:456:intry_do': The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first. from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:571:in
block in try_compile'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:524:inwith_werror' from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:571:in
try_compile'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:1060:inblock in have_header' from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:911:in
block in checking_for'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:351:inblock (2 levels) in postpone' from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:321:in
open'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:351:inblock in postpone' from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:321:in
open'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:347:inpostpone' from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:910:in
checking_for'
from /opt/vagrant/embedded/lib/ruby/2.2.0/mkmf.rb:1059:inhave_header' from extconf.rb:16:in
extconf failed, exit code 1
Gem files will remain installed in /Users/rui/.vagrant.d/gems/gems/ffi-1.9.14 for inspection.
Results logged to /Users/rui/.vagrant.d/gems/extensions/universal-darwin-12/2.2.0/ffi-1.9.14/gem_make.out
I think it would be nice to add a note about the fact that if you want to bind-fs the default /vagrant
folder, you need to first disable it.
Actually, I think that a full example on how to do this should be added, as it is probably the most common usage.
Not sure where you would like to see this put in the readme so the example could reference those lines I required:
config.vm.synced_folder ".", "/vagrant", disabled: true
config.vm.synced_folder ".", "/vagrant-nfs", type: "nfs"
config.bindfs.bind_folder "/vagrant-nfs", "/vagrant"
I hope I don't miss anything here as I am pretty unused to bind-fs ;)
And thanks for the plugin anyway, saved me a lot of time !
I've been beating up against this for a day or so, and I'm not even sure if I'm in the right place. This appears to only occur while trying to install the bindfs plugin.
the error I keep getting is
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing vagrant-bindfs (0.4.12), and Bundler cannot continue.
Make sure that `gem install vagrant-bindfs -v '0.4.12'` succeeds before bundling.
Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::InstallError: vagrant-bindfs requires Ruby version ~> 2.0.0.
EDIT:TLDR for anyone who stumbles here- "vagrant plugin install vagrant-bindfs --plugin-version '0.4.11'"
fixes this if you're trying to get past this error for a vagrant up
Vagrant 1.8.7 - reverted to 1.8.6 because of current curl issues
Bundler version 1.12.5
ansible 2.0.2.0
osx 10.12.1
ruby 2.3.2
gem install vagrant-bindfs -v '0.4.12'
fails with
ERROR: Error installing vagrant-bindfs:
vagrant-bindfs requires Ruby version ~> 2.0.0.
As noted, I'm using Ruby 2.3.2
disabling multisource fails as well (I've cleared my gem cache and cleaned my gems up as well)
Also found this as scheduled for the next release of vagrant
core: Remove Bundler integration for handling internal plugins [GH-7793, GH-8000, GH-8011]
annd your tweet about Rubygems/bundler merging.
:P lelz, I feel like I may have just gotten caught in a limbo period with this. Still wanted to go ahead and give you the heads up though in case you weren't already aware.
Hi,
I'm trying to get bindfs from a OSX host to a debian (testing) guest.
I get this error while provisioning:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get update
Stdout from the command:
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [62.9 kB]
Get:2 http://security.debian.org/debian-security stretch/updates/main Sources [712 B]
Get:3 http://cdn-fastly.deb.debian.org/debian stretch InRelease [186 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian stretch/main Sources.diff/Index [27.9 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian stretch/main Sources.diff/Index [27.9 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian stretch/main amd64 Packages.diff/Index [27.9 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian stretch/main amd64 Packages.diff/Index [27.9 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian stretch/main Sources [6,780 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian stretch/main amd64 Packages [7,108 kB]
Reading package lists...
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
E: Could not open file /var/lib/apt/lists/httpredir.debian.org_debian_dists_stretch_main_source_Sources.diff_Index - open (2: No such file or directory)
E: Could not open file /var/lib/apt/lists/httpredir.debian.org_debian_dists_stretch_main_binary-amd64_Packages.diff_Index - open (2: No such file or directory)
Here's the line in the Vagrantfile:
config.bindfs.bind_folder "/path/to/dir", "/var/endpoint"
It looks like a permission issue... Do you have any advice to get it up and running?
Hello!
I've been trying to use your plugin on a CentOS release 6.7 (Final)
VM. First some context, I absolutely had to install bindfs
through the sources as yum
couldn't find bindfs
through the standard repositories. It was really nice to find such feature (good job!). It got installed in the standard location as expected, e.g. /usr/local/bin
Now it seems like the bindfs
validation appears broken a bit. It did detect bindfs
correctly through bindfs --help
when running as standard vagrant user but failed to execute it through sudo
.
First validation snippet from vagrant
debug log:
INFO ssh: Execute: bindfs --help (sudo=false)
DEBUG ssh: stdout:
Usage: bindfs [options] dir mountpoint
(... abridged ...)
DEBUG ssh: Exit status: 0
Next excerpt, exposing the problem. The sudo
session can't reach bindfs
and the plugin fails to detect that problem:
DEBUG ssh: Checking whether SSH is ready...
DEBUG ssh: Re-using SSH connection.
INFO ssh: SSH is ready!
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: (sudo=false)
DEBUG ssh: Exit status: 0
DEBUG guest: Searching for cap: bindfs_bindfs_version
DEBUG guest: Checking in: redhat
DEBUG guest: Checking in: linux
DEBUG guest: Found cap: bindfs_bindfs_version in linux
INFO guest: Execute capability: bindfs_bindfs_version [#<Vagrant::Machine: master (VagrantPlugins::ProviderVirtualBox::Provider)>] (redhat)
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: sudo bindfs --version | cut -d" " -f2 (sudo=false)
DEBUG ssh: stderr: sudo
DEBUG ssh: stderr: :
DEBUG ssh: stderr: bindfs: command not found
DEBUG ssh: stderr:
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: sudo -i bindfs --version | cut -d" " -f2 (sudo=false)
DEBUG ssh: stderr: -bash: bindfs: command not found
DEBUG ssh: Exit status: 0
INFO interface: detail: Bindfs 0.0 is installed
INFO interface: detail: master: Bindfs 0.0 is installed
master: Bindfs 0.0 is installed
Perhaps that should be used instead (notice the '
s) !
sudo -i 'bindfs --version | cut -d" " -f2'
Example:
[blah@vm vagrant]$ sudo bindfs --version | cut -d" " -f2
sudo: bindfs: command not found
[blah@vm vagrant]$ echo $?
0
[blah@vm vagrant]$ sudo 'bindfs --version | cut -d" " -f2'
sudo: bindfs --version | cut -d" " -f2: command not found
[blah@vm vagrant]$ echo $?
1
Also, considering that obviously bindfs will fail in this context, I think it would be worth retrieve the full path and invoke it with the full path in the sudo session
[blah@vm vagrant]$ type bindfs
bindfs is /usr/local/bin/bindfs
Thank you a lot for this plugin!
I get this error when I vagrant up with vagrant-bindfs + vagrant-winnfsd:
Ubuntu 16.04.1 LTS vagrant tty1
vagrant login: [ 840.061101] INFO: task bindfs:2930 blocked for more than 120 seconds. [ 840.061136] Tainted: G OE 4.4.0-31-generic #50-Ubuntu
[ 840.061152] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
This is with Roots.io Trellis + Bedrock (WordPress), it just hangs at the Trellis line:
Install Dependencies with Composer.
I guess it is the first time that Trellis tries to connect to host disk, but I'm not sure about this.
This is on Windows 10 Pro x64, VirtualBox 5.1 and Vagrant 1.9.1, and latest Vagrant plugins after vagrant plugin update
Hi,
I'm running into an issue, that I can't find any solutions to (sudo gives the same result):
sad@sad-B551LA:$ vagrant --version$ vagrant plugin install vagrant-bindfs
Vagrant 1.8.1
sad@sad-B551LA:
Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
/usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in all=': undefined method
group_by' for nil:NilClass (NoMethodError)
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in with_isolated_gem' from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in
internal_install'
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:102:in install' from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:62:in
block in install_plugin'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:72:in install_plugin' from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in
call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in call' from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in
call'
from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in block in run' from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in
busy'
from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in run' from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in
action'
from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in block in execute' from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in
each'
from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in execute' from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in
execute'
from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in execute' from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:268:in
cli'
from /usr/bin/vagrant:173:in `
What do I do wrong?
/Henrik
We're using a Red hat -based distro that seems to not have wget installed (vagrant box scientific65_x86_64_minimal, distro https://www.scientificlinux.org/).
Installing bindfs fails with fresh vagrant due to missing wget. Would it be okay to add wget to yum package list in
vagrant-bindfs/lib/vagrant-bindfs/cap/redhat/install_bindfs.rb:14
comm.sudo("yum -y install fuse fuse-devel gcc wget")
?
I want to use bindfs with a user and group that does not exist on the VM until after it's been provisioned. bindfs fails during the initial vagrant up
due to the user not existing and prevents the provisioning from completing.
Do you think it would be practical to modify the plugin to optionally handle this scenario?
I added the following lines to my Vagrantfile
:'chmod-ignore'
:'chown-ignore'
:'chgrp-ignore'
I use bindfs since i have an application which needs to change the permission on the shared folder. When doing a command line:
$ chmod 775 platforms # works
When php -> chmod is triggering the change i get an Operation not permitted
I need to set shared folder relatively from vagrant directory. But vagrant return me
There are errors in the configuration of this machine. Please fix
the following errors and try again:
bindfs:
Hey, I've got a strange issue with using vagrant-bindfs. It looks like it's executing twice even though I have only one bindfs config line defined.
Here's the relevant output from vagrant up:
[base] Binding folders...
[base] -- /vagrant-nfs-code bind to /code/current
[base] Binding folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p
Vagrant version:
Vagrant version 1.0.5
My Vagrantfile is as follows:
Vagrant::Config.run do |config|
config.vm.define :base do |base_config|
base_config.vm.box = ""
base_config.vm.network :hostonly, "33.33.33.100"
base_config.vm.share_folder('code', '/vagrant-nfs-code', './code', :nfs => true)
base_config.bindfs.bind_folder("/vagrant-nfs-code", "/code/current")
end
end
I'll see if I can do any debugging myself, but I wanted to bring this to your attention.
Thank you!
Are you open for a rewrite/refactoring for the current vagrant plugin API? I would create a pull request for that including more capabilities for other distros. The other thing i would like to change is that i will replace the dashes in the options with underscores to make it valid symbols.
What do you think about it?
Just installed vagranf-bindfs with a fresh installation of vagrant. Vagrant up does not start due to an error with SOURCE_VERSION. Error information below:
/.vagrant.d/gems/gems/vagrant-bindfs-0.4.13/lib/vagrant-bindfs/config.rb:56:in `finalize!': uninitialized constant VagrantPlugins::Bindfs::SOURCE_VERSION (NameError)
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/v2/root.rb:50:in `block in finalize!'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/v2/root.rb:49:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/v2/root.rb:49:in `finalize!'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/v2/loader.rb:21:in `finalize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader.rb:168:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/vagrantfile.rb:28:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:746:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:746:in `vagrantfile'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:492:in `host'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:214:in `block in action_runner'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/runner.rb:33:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/runner.rb:33:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:479:in `hook'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb:728:in `unload'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:192:in `ensure in <main>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:192:in `<main>'
For several days now i can't mount my vagrant machine anymore.
Could not find the X.Org or XFree86 Window System, skipping.
An error occurred during installation of VirtualBox Guest Additions 5.0.6. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
stdin: is not a tty
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o 'vers=3,udp' 192.168.50.1:'/Users/fabianhenzler/Development/_marketplace/site' /vagrant-nfs-local.matrix42.com
Stdout from the command:
Stderr from the command:
stdin: is not a tty
mount.nfs: requested NFS version or transport protocol is not supported
We've had users happily using vagrant-bindfs 0.4.0, mostly on OS X host machines spinning up Ubuntu 14.04 VMs for a long time now with no problems. Suddenly we are getting reports of a lot of problem with vagrant-bindfs 0.4.6 and we have been having people downgrade to avoid the problem.
$ vagrant up
...
==> smstack: Exporting NFS shared folders...
==> smstack: Preparing to edit /etc/exports. Administrator privileges will be required...
==> smstack: Mounting NFS shared folders...
==> smstack: Mounting shared folders...
smstack: /vagrant => /Users/marca/dev/surveymonkey/smstack/smstack/ansible
==> smstack: Creating bind mounts for selected devices
/Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/command.rb:183:in `throw': uncaught throw :version (ArgumentError)
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/command.rb:183:in `block (3 levels) in bindfs_version'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:222:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:222:in `block (2 levels) in execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:497:in `block (3 levels) in shell_execute'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/channel.rb:569:in `call'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/channel.rb:569:in `do_data'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:567:in `channel_data'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:466:in `dispatch_incoming_packets'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:222:in `preprocess'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:206:in `process'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:170:in `block in loop'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:170:in `loop'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/session.rb:170:in `loop'
from /opt/vagrant/embedded/gems/gems/net-ssh-2.9.2/lib/net/ssh/connection/channel.rb:269:in `wait'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:589:in `shell_execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:215:in `block in execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:312:in `connect'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:209:in `execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/communicator.rb:259:in `test'
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/bind.rb:41:in `block in bind_folders'
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/bind.rb:37:in `each'
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/bind.rb:37:in `bind_folders'
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/bind.rb:21:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:160:in `handle'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:42:in `block in call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:41:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/env_set.rb:19:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/provision.rb:80:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /Users/marca/.vagrant.d/gems/gems/vagrant-bindfs-0.4.6/lib/vagrant-bindfs/bind.rb:14:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/set_name.rb:19:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/box_check_outdated.rb:36:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /Users/marca/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.1/lib/vagrant-hostsupdater/Action/RemoveHosts.rb:23:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
My host is Ubuntu 16.10 and my guest is Ubuntu 14.04 using Virtualbox. The bindfs plugin installed successfully on both the host and guest. I would like to use an NFS share and set the owner/group to a particular user, but I'm running into this error and I don't know how to debug it. Here's my Vagrant file:
If I remove the default_options and only use this, I still get the error:
config.vm.synced_folder "~/Documents/development/www", "/vagrant-nfs", type: :nfs config.bindfs.bind_folder "/vagrant-nfs", "/srv/users/serverpilot/apps/test/public"
Any hints would be most welcome.
Hi @gael-ian,
My team loves and heavily depends on your vagrant plugin, but recently we tripped over an issue regarding bindfs
Upstream Dependencies. Short version, vagrant-bindfs
depends on specific hard-coded versions of bindfs
, as defined in version.rb. bindfs
itself depends on FUSE, and newer versions of FUSE depend on newer versions of ruby and, well, dependency hell.
It would be super super helpful if vagrant-bindfs
would just let me optionally peg a specific version of bindfs
to go grab, falling back to whatever you've hardcoded to.
I can see two benefits here:
bindfs
without having to wait for you to push a new build of vagrant-bindfs
Hello, I get yellow info when start up my VM, have any fix for it?
==> default: Bindfs seems to not be installed on the virtual machine
==> default: Fuse kernel module seems to be not loaded, trying to load it
Thanks.
I am provisioning a box with puphpet and I need to run something as soon as it's up, but after the bindfs mounts are setup, is there a way to do that?
I'm tangentially aware of the issues with nfs shares on vagrant, but perhaps you could explain a little more fully in the README's plugin description how bindfs
solves these issues?
I'm just finding that I'm not quite understanding, and I would imagine you'd want people to understand the benefit of the plugin without having to install and test it first :)
At first I used the following setting:
config.bindfs.bind_folder /var/vagrant-bindfs/my/folder /my/folder
The mounts did not succeed and I received warnings when starting Vagrant:
There's already a bindfs mount to destination /my/folder
This appeared to be due to /var/vagrant-bindfs/my/folder
containing the word "bindfs", my workaround was using a different folder name, ie. /var/vagrant-nfs/my/folder
.
One solution is to change the first grep from
vagrant-bindfs/lib/vagrant-bindfs/bind.rb
Line 65 in 5085b6e
if @machine.communicate.test("mount | grep bindfs | grep #{command.destination}")
into ie.:
if @machine.communicate.test("mount | grep "^bindfs" | grep #{command.destination}")
Now only lines are grepped starting with "bindfs", though I do not know whether this works on Linux distributions other than my Ubuntu 14.04.
given the following configuration:
config.bindfs.bind_folder nfs_src, local_src, :'chown-ignore' => true, :'chgrp-ignore' => true
version 0.3.0 of this plugin seems to generate this command:
bindfs --force-user='vagrant' --force-group='vagrant' --perms='u=rwX:g=rD:o=rD' --chown-ignore --chgrp-ignore
unfortunately, thebindfs
command does not accept a force-user
option on my machine (ubuntu 12.04 with bindfs version 1.9).
as a workaround, i've asked people in my organization to install this plugin like so:
vagrant plugin install vagrant-bindfs --plugin-version 0.2.4
i saw some chat about mapping proper options to proper versions of bindfs. is someone working on that? it looks like the correct option in my case is --user
or --owner-user
instead of --force-user
(likewise for force-group
) but i haven't investigated what other incompatibilities exist.
Hi, someone know how config bindfs to keep multiples user:group in a single synced folder?
in my case: /home/vagrant/dpl
here my work environment
host ubuntu 16.04
guest ubuntu 16.04
vagrant-vbguest
vagrant-bindfs
...
config.vm.synced_folder "../dpl", "/home/vagrant/sync", type: :nfs
config.bindfs.bind_folder "/home/vagrant/sync", "/home/vagrant/dpl",
....
virtualbox > vagrant > docker
docker create multiple user:groups as it need...
main
root:root
mysql
vboxadd:vboxsf
content
www-data:www-data
thanks in advance,
--user
and --owner
options are deprecated:
https://github.com/mpartel/bindfs/blob/master/ChangeLog#L52-L58
Following error is raised on bindfs >=1.12 (assumed, tested with 1.12.3):
The bind command "bindfs --perms=u=rwX:g=rwX:o=rD --user=www-data --group=www-data /mnt/vagrant-index /var/www" failed to run!
Please check options values and compatibility. For a complete documentation,
run `sudo bindfs --help` on the VM.
Although one would expect it to continue work up until 1.13, it does not.
The new option names are --force-user
and --force-group
edit
I see it is actually not an issue of vagrant-bindfs
, rather a user of this plugin (puphpet). You can set the options here 1:1 as you would using bindfs via command line.
closed for this reason.
1st: great plugin!
Q: Is a vagrant version 2 support planned?
Hi, first of all thank you for making this great plugin ;)
In the latest version I'm unable to disable some options by passing in nil
as the value. I've taken a look at the source and it seems to me that VagrantBindfs::Bindfs::OptionSet.cast_option_as_value
is converting the nil
values to empty strings, therefore those options are passed to the actual bindfs command instead of being disabled.
Do you provide any other way to disable options?
Thanks
I get a message when creating the vm
=> web: Bindfs seems to not be installed on the virtual machine
Is this something I should be concerned about? Everything seems to be working on my vm but that message concerns me because a simple which bidnfs
reveals that it is infact installed on the box I'm using. Incidentally the default 'ubuntu/trusty64'
Enabling the multithreaded option for bindfs doesn't work:
Vagrant Config Snippet:
local_ebweb1.bindfs.bind_folder "/mnt/src", "/src",
:"multithreaded" => true,
:"chown-ignore" => true,
:"chgrp-ignore" => true,
:"chmod-ignore" => true,
:perms => "u=rwx:g=rwx:o=rx",
:user => 1500,
:group => 1500
Running process in linux guest: (no --multithreaded option)
bindfs --perms=u=rwx:g=rwx:o=rx --chown-ignore --chgrp-ignore --chmod-ignore --user=1500 --group=1500 /mnt/src /src
Thanks for this plugin, it's been a life save with a dev setup I'm working on, just one thing...
How do I set the nonempty option? On the cli it's -o nonempty
HI.I have some problem using vagrant-bindfs on win10.
My vagrangfile:
config.vm.synced_folder "D:/vagrant_share/", "/vagrant_data",type: :nfs
config.bindfs.bind_folder "D:/vagrant_db" ,"/vagrant_db",:owner => "mysql" ,:group => "mysql"
But,when i vagrant up ,it always post this error:
default: Cannot bind source path D:/vagrant_db because it doesn't exist
Oh,i really sure that the dir is exist!
Need some help.....
I have an issue with vagrant 1.4.3. After installing the plugin, vagrant tells me that it can't find the plugin... I'm on ubuntu 14.10, here's the details :
$ vagrant plugin install vagrant-bindfs
Installing the 'vagrant-bindfs' plugin. This can take a few minutes...
Installed the plugin 'vagrant-bindfs (0.3.2)'!
$ vagrant up
The plugin "vagrant-bindfs" could not be found. Please make sure that it is
properly installed via vagrant plugin
. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use plugin install
with a 1.0.x plugin.
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:
Vagrant:
$ vagrant -v
Vagrant 1.4.3
Hello,
Is it possible to force an owner and group to a specific repertory ?
I have many folders and I would like my symfony project get main-api.
Actually I have vagrant in each folders and get permission denied during my docker-compose up
Thanks for your help
This plugin relies on http://bindfs.org/downloads/ as location for the library. At the moment the site is gone, domain is parked. I'm not aware of official mirrors.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.