Hi folks.
I'm looking for general advice on how to manage vagrant plugins when
building VMs which many people on different machines.
Lately I've found that nokogiri can be a platform dependent plugin that can
wreak havoc on Vagrantfile's which use certain very common plugins.
Any advice for ma
hello,
after kernel upgrade, in the next reboot you need to recompile the
virtualbox modules
/etc/init.d/vboxadd setup
service vboxadd setup
On Thu, Jul 24, 2014 at 2:00 PM, James Chao wrote:
> Hi,
>
> I am using a box-cutter/centos64 image. I updated the kernel from
> 2.6.32-358 to 2.6
Hi,
I am using a box-cutter/centos64 image. I updated the kernel from
2.6.32-358 to 2.6.32-431.20.3
Then I did a vagrant halt / up. I got this. I am pretty sure the shared
folder was working, but it is not working anymore.
Anyone knows how to fix it ? Thanks
James
$ vagrant up
Bringing
if the paths are local, can you try reltive path?
but if the name of the directory is too long, can you try this?
http://serverfault.com/questions/163419/window-256-characters-path-name-limitation
On Thu, Jul 24, 2014 at 3:00 AM, Florian Tatzel wrote:
> I now digged deeper into the Issue.
>
I now digged deeper into the Issue.
I try to run everything with an easy to use Bash Script.
Windows shortens the Path and Vagrant doesnt seem to be able handling short
Path names such as "TUTORI~2" or searching in the wrong locations.
Using a short folder name like "VM/a" will work fine, but this
https://vagrantcloud.com/discover/featured
Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
g...@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriousl
Hi,
Has anyone worked with the ubuntu/trusty64 bit box? When I downloaded and
booted the vm, I was under the assumption that it was a 64-bit vm.
However, if I open up VirtualBox directly it's showing it as a 32 bit
system. Does anyone know about this or where we can get an 64 bit ubuntu
box
Hello,
When I use the Chef-Solo with recipe_url, I receive the error bellow:
/usr/lib/ruby/1.9.1/open-uri.rb:346:in open_http': 407 Proxy Authentication
Required (OpenURI::HTTPError) from /usr/lib/ruby/1.9.1/open-uri.rb:775:in
buffer_open'
from /usr/lib/ruby/1.9.1/open-uri.rb:203:in block in o
Is there a straightforward way of modifying the behavior of one of the
plugins that are shipped with vagrant? Looking to make a small-ish change
to the hyper-v provider and hoping there's an easier way than manually
modifying the relevant files in each vagrant install we've got. Is it
possible
Having access to the provider sounds useful, did anyone already create an
issue for it?
https://github.com/mitchellh/vagrant/issues
On Mon, Jul 21, 2014 at 10:09 PM, Benjamen Keroack
wrote:
> I just had to implement the hack from earlier in the thread (involving
> ARGV).
>
> Basically I need t
10 matches
Mail list logo