https://github.com/juanje/lxc-builder
A LXC template with Chef cookbooks to create a development enviroment for Aentos projects
https://github.com/juanje/lxc-builder
bash bootstrap chef lxc lxc-container provision shunit2
Last synced: 5 months ago
JSON representation
A LXC template with Chef cookbooks to create a development enviroment for Aentos projects
- Host: GitHub
- URL: https://github.com/juanje/lxc-builder
- Owner: juanje
- Created: 2012-10-03T00:58:57.000Z (over 13 years ago)
- Default Branch: master
- Last Pushed: 2012-11-30T07:43:17.000Z (over 13 years ago)
- Last Synced: 2023-04-12T13:02:26.545Z (about 3 years ago)
- Topics: bash, bootstrap, chef, lxc, lxc-container, provision, shunit2
- Language: Shell
- Size: 503 KB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Description
===========
This is a set of scripts to build a LXC container and prepare it to be provisioned by `chef-solo`.
This is meant to work with Debain and Ubuntu containers to be bootstraped with Chef. It also comes with a list of cookbooks to be used by the container in order to bootstrap an Rails project by any of the Aentos developers.
Install
=======
To install the scripts you need to have installed in a Ubuntu/Debian box with the following dependencies:
* `lxc`
* `make`
Now you need to run:
```
$ sudo make
```
It will install the scripts to `/usr/local/bin/`.
NOTE: It's important to run the `make` with `sudo` or as a root user.
You also can especify the `DESTDIR` and the `prefix` variables to the `make` command:
```
$ make DESTDIR=~ prefix=
```
It will install the scripts to `/home/$USER/bin`.
Usage
=====
First you need to run the `sudo rake`. Then you can create a LXC container with `lxc-build-project`:
```
$ sudo lxc-build-project -n [-u|--distro ] [-D|--distro ] [-- ]
```
Obviously, the `` you choose will be the one use to refer to the container. This parameter must be provider.
The `` is the name of the user you want to be created inside the container to manage it. It's optional but highly recommended to be provided.
If you are going to use the boostrap cookbook, **it's very important that the user you choose be the same in both cases** (the container and the cookbook). See the cookbook's attributes for more info.
The `` could be either `debian` or `ubuntu`. The default option is `debian`.
To create a LXC project it's enough to run (being `superproject` the name of the new project):
```
$ sudo lxc-build-project -n superproject
```
You can also pass some parameters to the `lxc-create` after `--`, like the IP the container should have:
```
$ sudo lxc-build-project -n superproject -- -i 10.0.3.51 -B lvm
```
After you create the container you need to provision it by doing:
```
$ sudo lxc-provision -n superproject -b /mnt/disk1/code/Berksfile
```
You will need a `Berksfile` file with the cookbooks for the project you want to bootstrap. A example is provider in this repo.
To know more about the `Berksfile`'s format please visit [the Berkshelf's site](http://berkshelf.com).
You also can use `lxc-console` or normal ssh connection to work inside the container. To connect via ssh with the container without password you can use a private key copied to `/var/cache/lxc/id_project_[container-name]` for this purpose.
There is also a handy command `lxc-ssh` which do the job. Here is how you can use it:
```
$ lxc-ssh -n superproject
```
In case you need it, the password for the `ubuntu` user is `ubuntu`.
License and Author
==================
Author:: Juanje Ojeda ()
Copyright:: 2012, Aentos
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.