It really does ... don't know why I didn't just add the extra file. I've fixed
this. Thanks!
> On Jun 21, 2017, at 6:32 AM, John Meinel wrote:
>
> Gotcha. Though I will say that looks more like its a bogus comment about a
> file that this isn't. But I see what you're doing.
>
> John
> =:->
>
Gotcha. Though I will say that looks more like its a bogus comment about a
file that this isn't. But I see what you're doing.
John
=:->
On Wed, Jun 21, 2017 at 5:29 PM, James Beedy wrote:
> It's in the comments at the top of the gist.
>
> On Jun 20, 2017, at 10:31 PM, John Meinel wrote:
>
> T
It's in the comments at the top of the gist.
> On Jun 20, 2017, at 10:31 PM, John Meinel wrote:
>
> This definitely sounds interesting.
>
> You included the layer python code, but not the "daemon.json.j2" file. Isn't
> that part of getting the networking config in place?
>
> John
> =:->
>
>
This definitely sounds interesting.
You included the layer python code, but not the "daemon.json.j2" file.
Isn't that part of getting the networking config in place?
John
=:->
On Wed, Jun 21, 2017 at 6:16 AM, James Beedy wrote:
> On integrating docker and lxd deployed apps ...
>
> My charm in
On integrating docker and lxd deployed apps ...
My charm includes layer-docker, and exposes a simple api wrapping docker-py
to allow the charm to login to dockerhub, pull and run docker images, and a
few other standard docker ops. My dockerized apps talk to elasticsearch,
mysql, and redis, all of
