It seems Jorge omitted why this is useful. When doing charm reviews or performing charm testing (while developing) you can use the docker container to quickly spin up an isolated environment so the charm can execute it's testing dependencies without dirtying the testers system. We're also now using the charmbox in the Charm CI system so it provides a consistent testing experience from our CI systems to your machine.
Marco On Fri, Mar 27, 2015 at 12:04 PM Nate Finch <nate.fi...@canonical.com> wrote: > What does this do that just using the juju binary on your local system > doesn't do? > > On Fri, Mar 27, 2015 at 11:49 AM, Jorge O. Castro <jo...@ubuntu.com> > wrote: > >> Hi everyone, >> >> First, if you haven't seen this yet, this is a docker container that >> let's you just try Juju, with the limitation that you can't do the >> local provider. >> >> - https://registry.hub.docker.com/u/whitmo/jujubox/ >> - https://github.com/whitmo/jujubox >> >> And here's the new bits, Cory Johns has been working on making a juju >> docker container that is more useful for charm developers and testers >> (so it's a bit larger than the jujubox) >> >> - https://registry.hub.docker.com/u/johnsca/charmbox/ >> - https://github.com/juju-solutions/charmbox >> >> Again the limitation is you can't use the local provider, however if >> you're testing on public clouds then you should see dramatic workflow >> speed vs. using the vagrant boxes. >> >> PRs and feedback all welcome! >> >> -- >> Jorge Castro >> Canonical Ltd. >> http://juju.ubuntu.com/ - Automate your Cloud Infrastructure >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >> mailman/listinfo/juju >> > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju