Closed warren5236 closed 5 years ago
Hello,
As a workaround, you can force bindfs installation from source . I'll try to find some time to take a look at what happened to the bindfs RPM package in CentOS 6 (and 7) as soon as I can.
The bindfs RPM package is available in the EPEL repository, that may not have been activated in your box.
How to active the EPEL repository on CentOS:
First problem: both CentOS and Fedora are considered the same in vagrant-bindfs
(Red Hat boxes with yum as package manager) but Fedora boxes don't need this.
Second problem: it may not be a good idea to active it on every CentOS boxes while installing bindfs.
The simple fact you runned into this problem prove this test to find if bindfs is available as a RPM package is wrong.
@gael-ian alpine (apk) support 👍
Hello @brunowego
I suppose your short message means you'd like to see vagrant-bindfs to support Alpine Linux guest machines. In this case, please take the time to open a dedicated issue and, if you can, to find a test box available on Vagrant Cloud and well maintained (as asked in vagrant-bindfs' Vagrantfile. Sadly, there is no official Alpine Linux box). A link to the Alpine package manager documentation can greatly help too, as I'm not user of this OS and know nothing about its arcanes.
Thanks
HI @warren5236,
I'm sorry that I did not took the time to fix this issue earlier but the new 1.1.1 release is now available. The problem was in the bindfs package detection via yum: in CentOS 7 it returns "No matches found" when it doesn't found an appropriate package, in CentOS 6 it returns "No Matches found"...
I switched to another method that detect when the package is available instead of when it's not and now the problem is fixed.
Thank you for your patience
Thank you for providing such an awesome plugin!
Hello, I'm using bento/centos-6.9 for a vagrant box and when I attempt to vagrant up I receive the following error message:
Any idea on how to solve this?