bgallet
/
0k-charms
forked from 0k/0k-charms
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
fork 0k-charms
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
624 Commits
37 Branches
0 Tags
43 MiB
 
 
Tree: 30d34777c4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '30d34777c4'
${ noResults }
0k-charms/precise/docker-builder
Valentin Lab 30d34777c4
new: doc: [rocketchat] add sentence to stress the limitation of the migration mecanism 		10 months ago
..
hooks fix: [docker-builder,host] update path when using ``0k-docker`` scripts 6 years ago
src/usr new: [docker-builder] using new aufs_apply and cleaned output. 10 years ago
README new: [docker-builder] added new charm. 10 years ago
config new: [docker-builder] added new charm. 10 years ago
metadata.yaml new: [docker-builder] added new charm. 10 years ago

README 



Unfinished because untested. But, the script docker-updater is
tested and used.


This LXC requires a kernel >3.8 at least. (to be able to run docker in
LXC) It requires also "aufs" capabilities (apparmor.d permission, but
also available in kernel)

XXXvlab: we could run docker in LXC via a socket towards an host's
install of docker and remove this constraint.


It is meant to build image of applications based on a single git-sub
code.

It provides an IMAGE that does not requires 'git' tool, and won't
contain any git history.

Then, it'll be able to update this image by small "docker commits"
quite efficiently.


Currently the image produced can only be run on docker host that
support running aufs in the containers (this implies, that the docker
fs driver IS NOT aufs, that the host kernel support aufs, and that
permissions are set so that container can mount an aufs filesystem).