Hey Charles!. the vbox is already running with 2GB of ram, and I have another vbox with Trusty too, and its working. Maybe is something related to "cannot clone a running container", or it's just an error caused by other thing.
I'm going to try to build everything again. Cheers, Sebas. 2014-05-18 14:19 GMT-03:00 Charles Butler <[email protected]>: > Sebas, > > Thanks for the report. I've reproduced this when the running vagrant image > didn't have enough allocated ram. If you bump the system ram to 2GB do you > see the same behavior? > > > > > On Sun, May 18, 2014 at 12:50 PM, Sebastian <[email protected]> wrote: > >> Hey people! >> >> I tested the new JujuTrusty box for the vagrant workflow, but! the lxc >> couldn't clone the container with the template, so the machines where never >> instantiated. After deployed 2 charms, mysql and drupal, this is what i got: >> >> machine-0: 2014-05-18 06:26:32 ERROR juju.provisioner >> provisioner_task.go:443 cannot start instance for machine "2": template >> container "juju-precise-template" did not stop >> machine-0: 2014-05-18 06:26:33 ERROR juju.container.lxc lxc.go:179 lxc >> container cloning failed: *cannot clone a running container* >> machine-0: 2014-05-18 06:26:33 ERROR juju.provisioner >> provisioner_task.go:443 cannot start instance for machine "3": cannot clone >> a running container >> machine-0: 2014-05-18 16:51:23 ERROR juju.rpc server.go:506 error writing >> response: EOF >> >> Cheers!, >> Sebas. >> >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >> >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
