>This would effectively make Docker another case of "syntactic sugar",
>much like OS::SoftwareConfig::Chef would be.
>Short term I think this will get Docker onto Heat users' instances
>quicker.
Agreed.
>However I do think that the limitations of this approach are pretty
>large, such as how to m
Excerpts from Andrew Plunk's message of 2014-05-20 13:49:58 -0700:
> No Problem.
>
> As the Docker resource in Heat currently works, it will require Docker
> running on a customer's vm to listen over a network socket. With software
> config you could allow Docker to listen on the instance's loca
No Problem.
As the Docker resource in Heat currently works, it will require Docker running
on a customer's vm to listen over a network socket. With software config you
could allow Docker to listen on the instance's local unix socket, and
communicate with Docker via Heat's in instance software c
>
>
> The solution I propose to this problem is to integrate docker with
> software config, which would allow the Docker api running on a compute
> instance to listen on an unix socket
>
First, thank you for looking at this.
Docker already listens on a unix socket. I'm not as familiar with Heat'
