Thanks. It's an interesting and useful idea.
Note that, in oneiric, you can do something similar using LVM snapshots.
Once you have an LVM container (automation of which is trivial but not
yet automated by a tool in the package :) you can
lxc-clone -s -o basecontainer -n tmpcontainer
lxc-start -n tmpcontainer
which takes about 3 seconds altogether. When done, destroy
tmpcontainer.
So one alternative workflow for this would be to extend lxc-clone
to support aufs as an alternative to lvm, using your model. So then
start an aufs container would be a two-step process, i.e.
lxc-clone --aufs -o basecontainer -n tmpcontainer
lxc-start -n tmpcontainer -d
lxc-destroy -n tmpcontainer
It's an extra step at startup, but OTOH it allows tmpcontainer to
more easily persist, sort of like schroot sessions. You could then
also script the steps into a single 'lxc-aufsstart'.
Does that sound sufficiently useful to you, or do you see advantages
to extending lxc-start to have a --aufs option to emulate your script?
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807351
Title:
it would be cool to be able to clone an lxc container onto aufs for
test runs - ephemeral containers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/807351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
