Thanks. :-)
I do hope we can also to get local provider working inside the
container as well, since it will provide a cleaner set of instructions
for new charmers to test their charms, or just play around with Juju.
But the --net=host workaround gives us immediate wins in CI, review,
and
On 27 March 2015 at 23:50, sheila miguez she...@pobox.com wrote:
On Fri, Mar 27, 2015 at 10:49 AM, Jorge O. Castro jo...@ubuntu.com wrote:
let's you just try Juju, with the limitation that you can't do the
local provider.
I definitely appreciate the ability to test something isolated from
That's great to hear that we're addressing issues that our community hasn't
been very vocal about yet.
I feel that the isolation story we're developing with this docker image is
really going to help the developer/testing story. Cory Johns has put in
some work and instructions on how to leverage
I just finished building a docker image for anyone who wants to test
juju 1.23-beta2 in a clean environment. By default, it'll setup a new,
persistent environment:
docker run -ti adamisrael/juju-1.23 -v
$HOME/.juju-1.23:/home/ubuntu/.juju
I intend to maintain images for each released version
I'm working on juju local/LXC support, in the hopes of improving the
developer workflow cross-platform.
On 2015-03-27 10:50 AM, sheila miguez wrote:
On Fri, Mar 27, 2015 at 10:49 AM, Jorge O. Castro jo...@ubuntu.com
mailto:jo...@ubuntu.com wrote:
let's you just try Juju, with the
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
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
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
Using the docker box is a complete isolation from your local system. We're
building docker images to scratch some itches:
- Run latest juju in full isolation so we can test the new features as they
land
- Isolate dependencies during charm reviews. (00-setup as sudo on your
system leaves WHAT
And here's a docker image of juju trunk:
docker run -ti -v $HOME/.juju-trunk:/home/ubuntu/.juju
adamisrael/juju-trunk
This is a nightly build of trunk, for those of us who want to explore
the bleeding edge. The image contains the go compiler, git, and the
source installed under ~/.go/. It
Addendum: the actual command to run is:
docker run -ti -v $HOME/.juju-1.23:/home/ubuntu/.juju
adamisrael/juju-1.23
On 2015-03-27 11:43 AM, Adam Israel wrote:
I just finished building a docker image for anyone who wants to test
juju 1.23-beta2 in a clean environment. By default, it'll
11 matches
Mail list logo
