ansible rant
ansible rant
Posted Oct 21, 2015 8:45 UTC (Wed) by picca (subscriber, #90087)In reply to: ansible rant by mathstuf
Parent article: Red Hat acquires Ansible
In fact propellor is also run in the container, in order to setup all the properties you defined for it.
This is the nice part of propellor,
container or host you define the properties the same way :).
Posted Oct 21, 2015 12:48 UTC (Wed)
by mathstuf (subscriber, #69389)
[Link] (2 responses)
[1]https://propellor.branchable.com/todo/spin_without_remote...
Posted Oct 22, 2015 4:10 UTC (Thu)
by joey (guest, #328)
[Link] (1 responses)
So, you could run propellor inside a chroot/container of the buildroot images without increasing their size.
Posted Oct 24, 2015 18:19 UTC (Sat)
by mathstuf (subscriber, #69389)
[Link]
Basically my goal is to have a repo for *building* images using Buildroot and adds the generated images to the git repository as refs/images/$name/base (explicit refs used so that old images aren't cloned by default and don't take up disk space past the reflog history length). Propellor would then grab these tarballs from git and configure them. It'd be nice to tar the configured images up and put them in as refs/images/$name/latest which is then also created as refs/images/$name/deployed when deployed as well.
First is getting all of the services I use available in buildroot…but I can at least play around with those which are already available.
ansible rant
ansible rant
ansible rant