vagrant-lxc 0.3.4 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c50dc38cceb25885011a091ace53495f0992bb45
-  data.tar.gz: d9e0c2cb8b70ff4a170d1744f438ffffcdaca199
+  metadata.gz: 70552f58b3dff461e6c8f585b581fcbe48eb8e33
+  data.tar.gz: 1e83aa6c65f3c3d82f78902db6def724fe13c262
 SHA512:
-  metadata.gz: a71590125708f5bdb688a46fc5e6d282e3acb49c9045946becb261a856b7f6a23b29b2bef25370c8d6bc9de23f765cf27f2e3e6a2e6442fe030dde5d8442fc31
-  data.tar.gz: 380309703b319c8eb6e91be92a8e2e1a09f28164d1076753667253ea9eb1a9b2b36ec11cffec8a1667d886cb32395ef2f5f44eab51c216e3a1e5bb66539cc45f
+  metadata.gz: d9c31869f568c381c36b49f5a2653d1479cb4598bb58c8b277afdd7e35b09f7db5613a493fe8eac58761cc23cc4dea52f93286a2883b3917fd59bbaaf8e29ee4
+  data.tar.gz: c82b8cb7240620f0d7e23e7969d73f16cf35752ef8044927de2fe3a027cf864cdb0b8819844bb6ace0d9f0afcc70dc07f1598db43b5f3d2707827e9af542e577

data/CHANGELOG.md

@@ -1,4 +1,19 @@
-## [0.?.?](https://github.com/fgrehm/vagrant-lxc/compare/v0.3.3...master)
+## [0.4.0](https://github.com/fgrehm/vagrant-lxc/compare/v0.3.4...master) (unreleased)
+
+FEATURES:
+
+  - New box format [#89](https://github.com/fgrehm/vagrant-lxc/issues/89)
+
+BUG FIXES:
+
+  - Add translation for stopped status [#97](https://github.com/fgrehm/vagrant-lxc/issues/97)
+  - Enable retries when fetching container state [#74](https://github.com/fgrehm/vagrant-lxc/issues/74)
+  - Fix error when setting Debian boxes hostname from Vagrantfile [#91](https://github.com/fgrehm/vagrant-lxc/issues/91)
+  - BTRFS-friendly base boxes [#81](https://github.com/fgrehm/vagrant-lxc/issues/81)
+  - Extended templates path lookup [#77](https://github.com/fgrehm/vagrant-lxc/issues/77) (tks to @aries1980)
+  - Fix default group for packaged boxes tarballs on the rake task [#82](https://github.com/fgrehm/vagrant-lxc/issues/82) (tks to @cduez)
+
+## [0.3.4](https://github.com/fgrehm/vagrant-lxc/compare/v0.3.3...v0.3.4) (May 08, 2013)
 
 FEATURES:
 
@@ -7,16 +22,21 @@ FEATURES:
 
 IMPROVEMENTS:
 
-  - Remove `/tmp` files after the machine has been successfully shut down [#68][]
+  - Replace `lxc-wait` usage with a "[retry mechanism](https://github.com/fgrehm/vagrant-lxc/commit/3cca16824879731315dac32bc2df1c643f30d461#L2R88)" [#22](https://github.com/fgrehm/vagrant-lxc/issues/22)
+  - Remove `/tmp` files after the machine has been successfully shut down [#68](https://github.com/fgrehm/vagrant-lxc/issues/68)
   - Clean up base boxes files after they've been configured, resulting in smaller packages
   - Bump development dependency to Vagrant 1.2+ series
 
+BUG FIXES:
+
+  - Issue a `lxc-stop` in case the container cannot shutdown gracefully [#72](https://github.com/fgrehm/vagrant-lxc/issues/72)
+
 ## [0.3.3](https://github.com/fgrehm/vagrant-lxc/compare/v0.3.2...v0.3.3) (April 23, 2013)
 
 BUG FIXES:
 
-  - Properly kill `redir` child processes [#59][]
-  - Use `uname -m` on base Ubuntu lxc-template [#53][]
+  - Properly kill `redir` child processes [#59](https://github.com/fgrehm/vagrant-lxc/issues/59)
+  - Use `uname -m` on base Ubuntu lxc-template [#53](https://github.com/fgrehm/vagrant-lxc/issues/53)
 
 IMPROVEMENTS:
 
@@ -39,20 +59,20 @@ BACKWARDS INCOMPATIBILITIES:
   - `start_opts` config was renamed to `customize`, please check the README for the expected parameters
   - V1 boxes are no longer supported
   - `target_rootfs_path` is no longer supported, just symlink `/var/lib/lxc` to the desired folder in case you want to point it to another partition
-  - Removed support for configuring private networks. It will come back at some point in the future but if you need it you should be able to set using `customize 'network.ipv4', '1.2.3.4'`
+  - Removed support for configuring private networks. It will come back at some point in the future but if you need it you should be able to set using `customize 'network.ipv4', '1.2.3.4/24'`
 
 IMPROVEMENTS:
 
   - lxc templates are removed from lxc template dir after container is created
   - Treat NFS shared folders as a normal shared folder instead of ignoring it so we can share the same Vagrantfile with VBox environments
-  - Support for lxc 0.7.5 (tested on Ubuntu 12.04) [#49][]
-  - Remove `/tmp` files when packaging quantal64 base box [#48][]
-  - Avoid picking the best mirror on quantal64 base box [#38][]
+  - Support for lxc 0.7.5 (tested on Ubuntu 12.04) [#49](https://github.com/fgrehm/vagrant-lxc/issues/49)
+  - Remove `/tmp` files when packaging quantal64 base box [#48](https://github.com/fgrehm/vagrant-lxc/issues/48)
+  - Avoid picking the best mirror on quantal64 base box [#38](https://github.com/fgrehm/vagrant-lxc/issues/38)
 
 BUG FIXES:
 
-  - Redirect `redir`'s stderr output to `/dev/null` [#51][]
-  - Switch from `ifconfig` to `ip` to grab container's IP to avoid localization issues [#50][]
+  - Redirect `redir`'s stderr output to `/dev/null` [#51](https://github.com/fgrehm/vagrant-lxc/issues/51)
+  - Switch from `ifconfig` to `ip` to grab container's IP to avoid localization issues [#50](https://github.com/fgrehm/vagrant-lxc/issues/50)
 
 ## [0.2.0](https://github.com/fgrehm/vagrant-lxc/compare/v0.1.1...v0.2.0) (March 30, 2013)
 
@@ -61,16 +81,16 @@ BUG FIXES:
 ## [0.1.1](https://github.com/fgrehm/vagrant-lxc/compare/v0.1.0...v0.1.1) (March 29, 2013)
 
   - Removed support for development under Vagrant < 1.1
-  - Removed rsync from base quantal64 box to speed up containers creation [#40][]
-  - Containers are now named after project's root dir [#14][]
+  - Removed rsync from base quantal64 box to speed up containers creation [#40](https://github.com/fgrehm/vagrant-lxc/issues/40)
+  - Containers are now named after project's root dir [#14](https://github.com/fgrehm/vagrant-lxc/issues/14)
   - Skip Vagrant's built in SSH redirect
-  - Allow setting rootfs from Vagrantfile [#30][]
+  - Allow setting rootfs from Vagrantfile [#30](https://github.com/fgrehm/vagrant-lxc/issues/30)
 
 ## [0.1.0](https://github.com/fgrehm/vagrant-lxc/compare/v0.0.3...v0.1.0) (March 27, 2013)
 
   - Support for chef added to base quantal64 box
   - Puppet upgraded to 3.1.1 on base quantal64 box
-  - Port forwarding support added [#6][]
+  - Port forwarding support added [#6](https://github.com/fgrehm/vagrant-lxc/issues/6)
 
 ## Previous
 

data/Gemfile

@@ -3,9 +3,10 @@ source 'https://rubygems.org'
 gemspec
 
 group :development do
-  # TODO: Lock to 1.2.3 once it is out with this fix: https://github.com/mitchellh/vagrant/pull/1685
-  gem 'vagrant', git: 'https://github.com/mitchellh/vagrant.git'
-  gem 'vagrant-cachier'
+  gem 'vagrant',          github: 'mitchellh/vagrant'
+  gem 'vagrant-cachier',  github: 'fgrehm/vagrant-cachier'
+  gem 'vagrant-pristine', github: 'fgrehm/vagrant-pristine'
+  gem 'vagrant-omnibus'
   gem 'guard'
   gem 'guard-rspec'
   gem 'rb-inotify'
@@ -14,7 +15,7 @@ end
 
 group :development, :test do
   gem 'rake'
-  gem 'rspec'
+  gem 'rspec',       '~> 2.13.0'
   gem 'rspec-fire',  require: 'rspec/fire'
   gem 'rspec-spies', require: false
   gem 'coveralls',   require: false

data/Gemfile.lock

@@ -1,12 +1,23 @@
 GIT
-  remote: https://github.com/mitchellh/vagrant.git
-  revision: ccfd321ef98dc5c12b180cc3a26f12d870c0eff5
+  remote: git://github.com/fgrehm/vagrant-cachier.git
+  revision: ae6cb5bcfbdbb2157867d77ded8f2b6f430c0f6c
   specs:
-    vagrant (1.2.3.dev)
+    vagrant-cachier (0.2.0)
+
+GIT
+  remote: git://github.com/fgrehm/vagrant-pristine.git
+  revision: 45a8d75f048bd611e337583496eb2b48b6998bbd
+  specs:
+    vagrant-pristine (0.1.0)
+
+GIT
+  remote: git://github.com/mitchellh/vagrant.git
+  revision: 6d26c86c4c3f65e2e59f4dda6bca9cd9235de704
+  specs:
+    vagrant (1.2.4.dev)
       childprocess (~> 0.3.7)
       erubis (~> 2.7.0)
       i18n (~> 0.6.0)
-      json (>= 1.5.1, < 1.8.0)
       log4r (~> 1.1.9)
       net-scp (~> 1.1.0)
       net-ssh (~> 2.6.6)
@@ -14,7 +25,7 @@ GIT
 PATH
   remote: .
   specs:
-    vagrant-lxc (0.3.4)
+    vagrant-lxc (0.4.0)
 
 GEM
   remote: https://rubygems.org/
@@ -31,36 +42,35 @@ GEM
       thor
     diff-lcs (1.2.4)
     erubis (2.7.0)
-    ffi (1.8.1)
+    ffi (1.9.0)
     formatador (0.2.4)
-    guard (1.8.0)
+    guard (1.8.1)
       formatador (>= 0.2.4)
       listen (>= 1.0.0)
       lumberjack (>= 1.0.2)
       pry (>= 0.9.10)
       thor (>= 0.14.6)
-    guard-rspec (2.6.0)
+    guard-rspec (3.0.2)
       guard (>= 1.8)
       rspec (~> 2.13)
     i18n (0.6.4)
-    json (1.7.7)
-    listen (1.0.3)
+    listen (1.2.2)
       rb-fsevent (>= 0.9.3)
       rb-inotify (>= 0.9)
       rb-kqueue (>= 0.2)
     log4r (1.1.10)
-    lumberjack (1.0.3)
+    lumberjack (1.0.4)
     method_source (0.8.1)
     mime-types (1.23)
-    multi_json (1.7.3)
-    net-scp (1.1.0)
+    multi_json (1.7.7)
+    net-scp (1.1.2)
       net-ssh (>= 2.6.5)
-    net-ssh (2.6.7)
-    pry (0.9.12.1)
+    net-ssh (2.6.8)
+    pry (0.9.12.2)
       coderay (~> 1.0.5)
       method_source (~> 0.8)
       slop (~> 3.4)
-    rake (10.0.4)
+    rake (10.1.0)
     rb-fsevent (0.9.3)
     rb-inotify (0.9.0)
       ffi (>= 0.5.0)
@@ -75,7 +85,7 @@ GEM
     rspec-core (2.13.1)
     rspec-expectations (2.13.0)
       diff-lcs (>= 1.1.3, < 2.0)
-    rspec-fire (1.1.3)
+    rspec-fire (1.2.0)
       rspec (~> 2.11)
     rspec-mocks (2.13.1)
     rspec-spies (2.1.4)
@@ -84,9 +94,9 @@ GEM
       multi_json (~> 1.0)
       simplecov-html (~> 0.7.1)
     simplecov-html (0.7.1)
-    slop (3.4.4)
+    slop (3.4.5)
     thor (0.18.1)
-    vagrant-cachier (0.0.2)
+    vagrant-omnibus (1.1.0)
 
 PLATFORMS
   ruby
@@ -97,9 +107,11 @@ DEPENDENCIES
   guard-rspec
   rake
   rb-inotify
-  rspec
+  rspec (~> 2.13.0)
   rspec-fire
   rspec-spies
   vagrant!
-  vagrant-cachier
+  vagrant-cachier!
   vagrant-lxc!
+  vagrant-omnibus
+  vagrant-pristine!

data/Guardfile

@@ -1,18 +1,7 @@
-guard 'bundler' do
-  watch('Gemfile')
-  watch(/^.+\.gemspec/)
-end
-
-guard 'ctags-bundler', :src_path => ["lib"] do
-  watch(/^(lib|spec\/support)\/.*\.rb$/)
-  watch('Gemfile.lock')
-end
-
-guard 'rspec' do
-  watch(%r{^spec/.+_spec\.rb$})
+guard 'rspec', :spec_paths => ["spec/unit"] do
+  watch(%r{^spec/unit/.+_spec\.rb$})
   watch(%r{^lib/vagrant-lxc/(.+)\.rb$}) { |m| "spec/unit/#{m[1]}_spec.rb" }
   watch('spec/unit_helper.rb')          { "spec/unit" }
-  watch('spec/acceptance_helper.rb')    { "spec/acceptance" }
-  watch('spec/spec_helper.rb')          { "spec/" }
-  watch(%r{^spec/support/(.+)\.rb$})    { "spec/" }
+  watch('spec/spec_helper.rb')          { "spec/unit" }
+  watch(%r{^spec/support/(.+)\.rb$})    { "spec/unit" }
 end

data/README.md

@@ -1,26 +1,46 @@
-# vagrant-lxc [![Build Status](https://travis-ci.org/fgrehm/vagrant-lxc.png?branch=master)](https://travis-ci.org/fgrehm/vagrant-lxc) [![Gem Version](https://badge.fury.io/rb/vagrant-lxc.png)](http://badge.fury.io/rb/vagrant-lxc) [![Code Climate](https://codeclimate.com/github/fgrehm/vagrant-lxc.png)](https://codeclimate.com/github/fgrehm/vagrant-lxc) [![Coverage Status](https://coveralls.io/repos/fgrehm/vagrant-lxc/badge.png?branch=master)](https://coveralls.io/r/fgrehm/vagrant-lxc)
+# vagrant-lxc
 
-Linux Containers support for Vagrant 1.1+
+[![Build Status](https://travis-ci.org/fgrehm/vagrant-lxc.png?branch=master)](https://travis-ci.org/fgrehm/vagrant-lxc) [![Gem Version](https://badge.fury.io/rb/vagrant-lxc.png)](http://badge.fury.io/rb/vagrant-lxc) [![Code Climate](https://codeclimate.com/github/fgrehm/vagrant-lxc.png)](https://codeclimate.com/github/fgrehm/vagrant-lxc) [![Coverage Status](https://coveralls.io/repos/fgrehm/vagrant-lxc/badge.png?branch=master)](https://coveralls.io/r/fgrehm/vagrant-lxc)
+
+[LXC](http://lxc.sourceforge.net/) provider for [Vagrant](http://www.vagrantup.com/) 1.1+
+
+This is a Vagrant plugin that allows it to control and provision Linux Containers
+as an alternative to the built in Vagrant VirtualBox provider for Linux hosts.
 
 Check out this [blog post](http://fabiorehm.com/blog/2013/04/28/lxc-provider-for-vagrant)
 to see the plugin in action and find out more about it.
 
-## Dependencies
+## Features
+
+* Vagrant's `up`, `halt`, `reload`, `destroy`, `ssh`, `provision` and `package`
+* Shared folders
+* Provisioning with any built-in Vagrant provisioner
+* Port forwarding
+* Setting container's host name
+
+*Please refer to the [closed issues](https://github.com/fgrehm/vagrant-lxc/issues?labels=&milestone=&page=1&state=closed)
+and the [changelog](CHANGELOG.md) for most up to date information.*
 
-* Vagrant 1.1+ (1.1.3+ recommended)
-* lxc 0.7.5+ (0.8.0-rc1+ recommended)
+
+## Requirements
+
+* [Vagrant 1.1+](http://downloads.vagrantup.com/)
+* lxc 0.7.5+
 * redir (if you are planning to use port forwarding)
-* A Kernel [higher than 3.5.0-17.28](#help-im-unable-to-restart-containers)
+* A [bug-free](#help-im-unable-to-restart-containers) kernel
 
-On a clean Ubuntu 12.10 machine it means something like:
+The plugin is known to work better and pretty much out of the box on Ubuntu 12.04+
+hosts and installing the dependencies on it basically means a `apt-get install lxc redir`
+and a `apt-get update && apt-get dist-upgrade` to upgrade the kernel.
 
-```
-sudo apt-get update && sudo apt-get dist-upgrade
-sudo apt-get install lxc redir
-# Downloads and install Vagrant 1.1.5
-wget "http://files.vagrantup.com/packages/64e360814c3ad960d810456add977fd4c7d47ce6/vagrant_`uname -m`.deb" -O /tmp/vagrant.deb
-sudo dpkg -i /tmp/vagrant.deb
-```
+Some manual steps are required to set up a Linode machine prior to using this
+plugin, please check https://github.com/fgrehm/vagrant-lxc/wiki/Usage-on-Linode
+for more information. The same applies to Debian hosts and documentation will be
+provided soon.
+
+If you are on a Mac or Windows machine, you might want to have a look at this
+blog post for some ideas on how to set things up: http://the.taoofmac.com/space/HOWTO/Vagrant
+or use use the same [Ubuntu 12.10 VirtualBox machine I use for development](https://github.com/fgrehm/vagrant-lxc/wiki/Development#using-virtualbox-for-development).
 
 
 ## Installation
@@ -32,185 +52,82 @@ vagrant plugin install vagrant-lxc
 
 ## Usage
 
-After installing, add a [base box](#available-boxes) using any name you want, for example:
+After installing, add a [base box](#base-boxes) using any name you want, for example:
 
 ```
-vagrant box add lxc-quantal64 http://dl.dropbox.com/u/13510779/lxc-quantal-amd64-2013-05-06.box
+vagrant box add quantal64 http://dl.dropbox.com/u/13510779/lxc-quantal-amd64-2013-07-12.box
 ```
 
-Make a Vagrantfile that looks like the following, filling in your information where necessary:
+Then create a Vagrantfile that looks like the following, changing the box name
+to the one you've just added:
 
 ```ruby
 Vagrant.configure("2") do |config|
-  # Change it to the name of the box you have just added
-  config.vm.box = "lxc-quantal64"
-
-  # You can omit this block if you don't need to override any container setting
-  config.vm.provider :lxc do |lxc|
-    # OPTIONAL: Same effect as as 'customize ["modifyvm", :id, "--memory", "1024"]' for VirtualBox
-    lxc.customize 'cgroup.memory.limit_in_bytes', '1024M'
-    # OPTIONAL: Limits swap size
-    lxc.customize 'cgroup.memory.memsw.limit_in_bytes', '512M'
-  end
+  config.vm.box = "quantal64"
 end
 ```
 
-And finally run `vagrant up --provider=lxc`. If you are using Vagrant 1.2+ you can
-also set `VAGRANT_DEFAULT_PROVIDER` environmental variable to `lxc`.
-
-If you are on a mac or window host and still want to try this plugin out, you
-can use the [same Vagrant VirtualBox machine I use for development](#using-virtualbox-for-development).
+And finally run `vagrant up --provider=lxc`.
 
-### Available boxes
+If you are using Vagrant 1.2+ you can also set `VAGRANT_DEFAULT_PROVIDER`
+environmental variable to `lxc` in order to avoid typing `--provider=lxc` all
+the time.
 
-| LINK | DESCRIPTION |
-| --- | ---         |
-| [lxc-raring-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-raring-amd64-2013-05-08.box) | Ubuntu 13.04 Raring x86_64 (Puppet 3.1.1) |
-| [lxc-quantal-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-quantal-amd64-2013-05-08.box) | Ubuntu 12.10 Quantal x86_64 (Puppet 3.1.1 & Chef 11.4.0) |
-| [lxc-precise-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-precise-amd64-2013-05-08.box) | Ubuntu 12.04 Precise x86_64 (Puppet 3.1.1 & Chef 11.4.0) |
-| [lxc-sid-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-sid-amd64-2013-05-08.box) | Debian Sid (Puppet 3.1.1) |
-| [lxc-wheezy-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-wheezy-amd64-2013-05-08.box) | Debian Wheezy (Puppet 3.1.1) |
-| [lxc-squeeze-amd64-2013-05-08.box](http://dl.dropbox.com/u/13510779/lxc-squeeze-amd64-2013-05-08.box) | Debian Squeeze (Puppet 3.1.1) |
 
-*Please note that I'm currently using only the quantal x86_64 on a daily basis,
-and I've only done some basic testing with the others*
+### Advanced configuration
 
-There is a set of [rake tasks](tasks/boxes.rake) that you can use to build base
-boxes as needed. By default it won't include any provisioning tool and you can
-pick the one you want by providing some environment variables.
+If you want, you can modify container configurations from within your Vagrantfile
+using the [provider block](http://docs.vagrantup.com/v2/providers/configuration.html):
 
-For example:
-
-```
-CHEF=1 rake boxes:ubuntu:build:precise64
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box = "quantal64"
+  config.vm.provider :lxc do |lxc|
+    # Same effect as as 'customize ["modifyvm", :id, "--memory", "1024"]' for VirtualBox
+    lxc.customize 'cgroup.memory.limit_in_bytes', '1024M'
+  end
+end
 ```
 
-Will build a Ubuntu Precise x86_64 box with chef pre-installed.
-
-### Storing container's rootfs on a separate partition
-
-Before the 0.3.0 version of this plugin, there used to be a support for specifying
-the container's rootfs path from the `Vagrantfile`, on 0.3.0 this was removed as you
-can achieve the same effect by symlinking or mounting `/var/lib/lxc` on a separate
-partition.
+This will make vagrant-lxc pass in `-s lxc.cgroup.memory.limit_in_bytes=1024M`
+to `lxc-start` when booting containers. This will override any previously value
+set from container's configuration file that is usually kept under
+`/var/lib/lxc/<container-name>/config`.
 
-### NFS shared folders
+For other configuration options, please check [lxc.conf manpages](http://manpages.ubuntu.com/manpages/quantal/man5/lxc.conf.5.html).
 
-NFS shared folders are not supported and will behave as a "normal" shared folder
-so we can share the same Vagrantfile with VBox environments.
 
+### Base boxes
 
-## What is currently supported?
-
-Pretty much everything you need from Vagrant:
-
-* Vagrant's `up`, `halt`, `reload`, `destroy`, `ssh` and `package` commands (box packaging is kind of experimental)
-* Shared folders
-* Provisioning
-* Setting container's host name
-* Port forwarding
-
-*Please refer to the [closed issues](https://github.com/fgrehm/vagrant-lxc/issues?labels=&milestone=&page=1&state=closed)
-and the [changelog](CHANGELOG.md) for most up to date information.*
+Please check [the wiki](https://github.com/fgrehm/vagrant-lxc/wiki/Base-boxes)
+for a list of [pre built](https://github.com/fgrehm/vagrant-lxc/wiki/Base-boxes#available-boxes)
+base boxes and information on [how to build your own](https://github.com/fgrehm/vagrant-lxc/wiki/Base-boxes#building-your-own).
 
 
 ## Current limitations
 
-* Does not detect forwarded ports collision, right now you are responsible for taking care of that
-* A hell lot of `sudo`s (this will probably be like this until [user namespaces](http://s3hh.wordpress.com/2013/02/12/user-namespaces-lxc-meeting/) are supported)
+* The plugin does not detect forwarded ports collision, right now you are
+  responsible for taking care of that.
+* There is a hell lot of `sudo`s involved and this will probably be around until
+  [user namespaces](https://wiki.ubuntu.com/LxcSecurity) are supported or I'm able to handle [#90](https://github.com/fgrehm/vagrant-lxc/issues/90)
 * [Does not tell you if dependencies are not met](https://github.com/fgrehm/vagrant-lxc/issues/11)
   (will probably just throw up some random error)
 * + bunch of other [core features](https://github.com/fgrehm/vagrant-lxc/issues?labels=core&milestone=&page=1&state=open)
   and some known [bugs](https://github.com/fgrehm/vagrant-lxc/issues?labels=bug&page=1&state=open)
 
 
-## Development
-
-If  want to develop from your physical machine, just sing that same old song:
-
-```
-git clone git://github.com/fgrehm/vagrant-lxc.git
-cd vagrant-lxc
-bundle install
-bundle exec rake # to run unit specs
-```
-
-To run acceptance specs, you'll have to ssh into one of the [development boxes](development/Vagrantfile) and run:
-
-```
-bundle exec rake spec:acceptance
-```
-
-To build the provided quantal64 box:
-
-```
-bundle exec rake boxes:quantal64:build
-vagrant box add quantal64 boxes/output/lxc-quantal64.box
-```
-
-### Using `vagrant-lxc` to develop itself
-
-Yes! The gem has been [bootstrapped](http://en.wikipedia.org/wiki/Bootstrapping_(compilers)
-and since you can boot a container from within another, after cloning the
-project you can run the commands below from the host machine to get a container
-ready for development:
-
-```sh
-# Required in order to allow nested containers to be started
-sudo apt-get install apparmor-utils
-sudo aa-complain /usr/bin/lxc-start
-bundle install
-cd development
-bundle exec vagrant up lxc --provider=lxc
-bundle exec vagrant ssh lxc
-```
-
-That should result in a container ready to be `bundle exec vagrant ssh`ed.
-Once you've SSH into the guest container, you'll be already on the project's root.
-Keep in mind that you'll probably need to run `sudo aa-complain /usr/bin/lxc-start`
-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.
-
-### Using VirtualBox for development
-
-```
-cd development
-bundle exec vagrant up vbox
-# A reload is needed to ensure the updated kernel gets loaded
-bundle exec vagrant reload vbox
-bundle exec vagrant ssh vbox
-```
-
-
-## Protips
-
-If you want to find out more about what's going on under the hood on vagrant,
-prepend `VAGRANT_LOG=debug` to your `vagrant` commands. For `lxc-start`s
-debugging set `LXC_START_LOG_FILE`:
-
-```
-LXC_START_LOG_FILE=/tmp/lxc-start.log VAGRANT_LOG=debug vagrant up
-```
-
-This will output A LOT of information on your terminal and some useful information
-about `lxc-start` to `/tmp/lxc-start.log`.
+## More information
 
+Please refer the [wiki](https://github.com/fgrehm/vagrant-lxc/wiki) for more
+information.
 
-## Help! I'm unable to restart containers!
 
-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
-(>= 3.5.0-17.28). More information can be found on:
+## Problems / ideas?
 
-* https://bugzilla.kernel.org/show_bug.cgi?id=47181
-* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471
-* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065434
-
-Sometimes the dev boxes I'm using are not able to `lxc-start` containers
-anymore. Most of the times it was an issue with the arguments I provided
-to it for customization (or a *buggy* kernel). If you run into that, rollback your changes
-and try to `vagrant reload` the dev box. If it still doesn't work,
-please file a bug at the [issue tracker](https://github.com/fgrehm/vagrant-lxc/issues).
+Please review the [Troubleshooting](https://github.com/fgrehm/vagrant-lxc/wiki/Troubleshooting)
+wiki page + [known bugs](https://github.com/fgrehm/vagrant-lxc/issues?labels=bug&page=1&state=open)
+list if you have a problem and feel free to use the [issue tracker](https://github.com/fgrehm/vagrant-lxc/issues)
+to ask questions, propose new functionality and / or report bugs.
 
 
 ## Similar projects
@@ -218,6 +135,7 @@ please file a bug at the [issue tracker](https://github.com/fgrehm/vagrant-lxc/i
 * [vagabond](https://github.com/chrisroberts/vagabond) - "a tool integrated with Chef to build local nodes easily"
 * [vagueant](https://github.com/neerolyte/vagueant) - "vaguely like Vagrant for linux containers (lxc)"
 
+
 ## Contributing
 
 1. Fork it