🟢 Stable | LXC provider for Vagrant (up-to-date & maintained)

Go to file

Fabio Rehm 55c9be772d Not so initial commit		2013-02-25 02:04:31 -03:00
lib	Not so initial commit	2013-02-25 02:04:31 -03:00
spec	Not so initial commit	2013-02-25 02:04:31 -03:00
tasks	Not so initial commit	2013-02-25 02:04:31 -03:00
vagrant-1.1@803269f729	Not so initial commit	2013-02-25 02:04:31 -03:00
.gitignore	Not so initial commit	2013-02-25 02:04:31 -03:00
.gitmodules	Not so initial commit	2013-02-25 02:04:31 -03:00
.rspec	Not so initial commit	2013-02-25 02:04:31 -03:00
.vimrc	Not so initial commit	2013-02-25 02:04:31 -03:00
config.yml.sample	Not so initial commit	2013-02-25 02:04:31 -03:00
Gemfile	Not so initial commit	2013-02-25 02:04:31 -03:00
Gemfile.lock	Not so initial commit	2013-02-25 02:04:31 -03:00
Guardfile	Not so initial commit	2013-02-25 02:04:31 -03:00
Rakefile	Not so initial commit	2013-02-25 02:04:31 -03:00
README.md	Not so initial commit	2013-02-25 02:04:31 -03:00
setup-vagrant-dev-box	Not so initial commit	2013-02-25 02:04:31 -03:00
Vagrantfile	Not so initial commit	2013-02-25 02:04:31 -03:00

README.md

vagrant-lxc

Highly experimental Linux Containers support for Vagrant 1.1

WARNING

Please keep in mind that this is not even alpha software and things might go wrong. Although I'm brave enough to use it on my physical machine, its recommended that you try it out on the Vagrant dev box ;)

Development

On your host:

./setup-vagrant-dev-box
vagrant ssh

On the guest machine:

mkdir /tmp/vagrant-lxc
cp /vagrant/config.yml.sample /tmp/vagrant-lxc/config.yml
cd /tmp/vagrant-lxc
/vagrant/lib/provider up
/vagrant/lib/provider ssh

Troubleshooting

If your container / dev box start acting weird, run vagrant reload to see if things get back to normal.

In case vagrant reload doesn't work, restore the VirtualBox snapshot that was created automagically right after ./setup-vagrant-dev-box finished by running the same script again and selecting the [r]estore snapshot option when asked.