Comment 4 for bug 1315216

You can use the "juju deploy --to lxc:0" or "juju deploy --to kvm:0" to
create a container on the same machine-0 as the other ones you are
creating. I'm not sure how that compares to what you are doing right now.

It certainly wasn't expect that the normal behavior would be to start a KVM
instance and then run 10 LXC instances inside of it. I certainly could see
a case for having a flag for using templates when deploying containers
inside of regular instances, but it does cause a large increase in initial
consumption if your target filesystem doesn't support cheap clones.

John
=:->

On Tue, May 6, 2014 at 8:09 PM, Adam Stokes <email address hidden>wrote:

> > Cloning support was only intended as a local provider feature due to
> potential issues with placing a large blob (the lxc template) into the
> kvm container.
>
> sorry, this statement is a little confusing, to clarify are you talking
> about local provider and LXC? As local provider supports both kvm/lxc
> and also we have the ability to deploy both kvm/lxc in the same
> environment. Since we can not run lxc 'machines' along side kvm
> 'machines' we have to nest those containers within a kvm machine. with
> that said should juju treat a kvm machine any differently than a bare
> metal machine via maas? the cloning features intended for a local
> provider deploy should not be limited to the machine creation but also
> available to the containers within a machine.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1315216
>
> Title:
> lxc nested within kvm machines do not use lxc-clone
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1315216/+subscriptions
>