glenux/vagrant-lxc-ng
glenux/vagrant-lxc-ng
1
0
Fork 0
Code Issues 4 Pull requests Projects 1 Releases Packages Wiki Activity

README update as usual

Browse source
This commit is contained in:
Fabio Rehm 2013-03-18 20:44:51 -03:00
parent 83076f4312
commit 3fe5977b8b
1 changed files with 16 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
README.md
View file

@ -4,9 +4,6 @@
Highly experimental Linux Containers support for Vagrant 1.1. Highly experimental Linux Containers support for Vagrant 1.1.
Please refer to the [closed issues](https://github.com/fgrehm/vagrant-lxc/issues?labels=&milestone=&page=1&state=closed)
to find out whats currently supported.
## Dependencies ## Dependencies
@ -23,10 +20,13 @@ sudo apt-get install lxc bsdtar fping
* Vagrant's `up`, `halt`, `reload`, `destroy`, and `ssh` commands * Vagrant's `up`, `halt`, `reload`, `destroy`, and `ssh` commands
* Shared folders * Shared folders
* Provisioners * Provisioning with shell scripts and puppet (should work with chef but I [haven't had the chance](https://github.com/fgrehm/vagrant-lxc/issues/37) to set it up on the base box)
* Setting container's host name * Setting container's host name
* Host-only / private networking * Host-only / private networking
*Please refer to the [closed issues](https://github.com/fgrehm/vagrant-lxc/issues?labels=&milestone=&page=1&state=closed)
for the most up to date list.*
## Current limitations ## Current limitations
@ -71,11 +71,8 @@ Vagrant.configure("2") do |config|
end end
``` ```
If you don't trust me and believe that it will mess up with your current Vagrant If you are on a mac or window host and still want to try this plugin out, you
installation and / or are afraid that something might go wrong with your machine, can use the [same Vagrant VirtualBox machine I use for development](#using-virtualbox-and-vagrant-11-for-development).
fire up the [same Vagrant VirtualBox machine I'm using for development](#using-virtualbox-and-vagrant-10-for-development)
to try things out and do the same as above. That might also get you up and running
if you are working on a mac or windows host ;)
## Development ## Development
@ -121,6 +118,15 @@ Keep in mind that you'll probably need to run `sudo aa-complain /usr/bin/lxc-sta
on the host whenever you want to hack on it, otherwise you won't be able to on the host whenever you want to hack on it, otherwise you won't be able to
start nested containers there to try things out. start nested containers there to try things out.
### Using VirtualBox and Vagrant 1.1 for development
```
cd development
ln -s Vagrantfile.1.1 Vagrantfile
bundle exec vagrant up vbox
bundle exec vagrant reload vbox
bundle exec vagrant ssh vbox
```
### Using VirtualBox and Vagrant 1.0 for development ### Using VirtualBox and Vagrant 1.0 for development
@ -132,16 +138,6 @@ vagrant reload
vagrant ssh vagrant ssh
``` ```
### Using VirtualBox and Vagrant 1.1 for development
```
cd development
ln -s Vagrantfile.1.1 Vagrantfile
bundle exec vagrant up vbox
bundle exec vagrant reload vbox
bundle exec vagrant ssh vbox
```
## Protips ## Protips
@ -157,9 +153,7 @@ This will output A LOT of information on your terminal and some useful informati
about `lxc-start` to `/tmp/lxc-start.log`. about `lxc-start` to `/tmp/lxc-start.log`.
## Help! ## Help! I'm unable to restart containers!
### I'm unable to restart containers!
It happened to me quite a few times in the past and it seems that it is related It happened to me quite a few times in the past and it seems that it is related
to a bug on linux kernel, so make sure you are using a bug-free kernel to a bug on linux kernel, so make sure you are using a bug-free kernel