[vagrant-up] working with Ubuntu 14.04, Virtualbox, and AWS

Hello, I'm a vagrant n00b. I'd like find a 64-bit Ubuntu 14.04 LTS box that I could use that would just work with both Virtualbox and AWS. There doesn't appear to be a 14.04 box for AWS: https://vagrantcloud.com/search?provider=awsq=14.04sort=utf8=%E2%9C%93 But there are a few for

[vagrant-up] Can Vagrant run a Docker image in the foreground, interactively?

Hello, I have a Vagrantfile that looks like this: # -*- mode: ruby -*- # vi: set ft=ruby : # Vagrantfile API/syntax version. Don't touch unless you know what you're doing! VAGRANTFILE_API_VERSION = 2 ENV['VAGRANT_DEFAULT_PROVIDER'] ||= 'docker' Vagrant.configure(VAGRANTFILE_API_VERSION) do

[vagrant-up] How to prevent users from running 'vagrant share'

Hello, We are using vagrant in our development team and its working very well, however I have some VERY serious concerns with 'vagrant share' as 'security by obscurity' is not really good enough for us. Is there anything I can put in my Vagrantfile or anywhere else to stop 'vagrant share'

[vagrant-up] What is the best way to install php 5.5 on Vagrant ?

Hello Everybody, I'm a recent user of Vagrant and i try to setup an development environment with php 5.5. I use Chef and php cookbook and my problem is the installed php version is always php 5.3. Any solutions? Thks. -- You received this message because you are subscribed to the Google

Re: [vagrant-up] What is the best way to install php 5.5 on Vagrant ?

Sounds like a chef problem not a vagrant problem. Vagrant simply runs the chef configuration. On Wed, Jun 4, 2014 at 4:46 PM, Gaël CRISPYN gael.cris...@gmail.com wrote: Hello Everybody, I'm a recent user of Vagrant and i try to setup an development environment with php 5.5. I use Chef and

Re: [vagrant-up] working with Ubuntu 14.04, Virtualbox, and AWS

Hi Dan, with vagrant-aws you are in luck because its basically just an empty dummy box, see here: https://github.com/mitchellh/vagrant-aws/#quick-start You can unzip the dummy.box file from here and have a look inside, then you'll see why it's called a dummy box:

Re: [vagrant-up] working with Ubuntu 14.04, Virtualbox, and AWS

Nice! I got it to work (the rsync is a little flaky but that's another thread). So if I understand this correctly, I can set up two config.provider.vm sections in my Vagrantfile, one for Virtualbox and one for AWS, and the appropriate one will be used depending on the --provider switch. As

Re: [vagrant-up] How to prevent users from running 'vagrant share'

On Tue, Jun 03, 2014 at 01:47:43PM -0700, marco romanini wrote: We are using vagrant in our development team and its working very well, however I have some VERY serious concerns with 'vagrant share' as 'security by obscurity' is not really good enough for us. Is there anything I can put in

[vagrant-up] Re: Vagrant, Windows Samba

Bumping this, I guess. I'm still having nothing but problems. I've solved the SSH issue by upgrading to Vagrant 1.6.3, but now I get the Failed to mount folders in Linux guest error. There's a LOT of chatter about this one around the Google-sphere, but none of it is getting me anywhere. I'm

Re: [vagrant-up] Re: Vagrant/Berkshelf `initialize': undefined method `opts'

Installed vagrant-bekrshelf 2.0.1 Now getting this.. Vagrant failed to initialize at a very early stage: The plugins failed to load properly. The error message given is shown below. uninitialized constant Chef::Provider::Package::Apt -- You received this message because you are subscribed to

Re: [vagrant-up] Problems with vagrant up --provider=kvm

On Wed, Jun 4, 2014 at 11:39 PM, Camila Cruz ccamila.cruz.san...@gmail.com wrote: no implicit conversion from nil to integer Hello, Seems the error is coming from the plugin and not from vagrant. Can you open a issue with the guys of vagrant-kvm?