tcp://host:port instead of /var/run/docker.sock? about envy HOT 5 CLOSED

I'm not sure I want to support non-socket Docker API ... means people will do weird stuff like try it with Swarm or remote hosts in general and that's not supported. Why do you want to use tcp?

from envy.

I have a Sun box for my docker system that I contact over tcp. No big deal,
just a nice to have. I was 'thinking' about swarm, so you already have me
down as a trouble maker ;-)
On 25 Jun 2015 20:01, "Jeff Lindsay" [email protected] wrote:

I'm not sure I want to support non-socket Docker API ... means people will
do weird stuff like try it with Swarm or remote hosts in general and that's
not supported. Why do you want to use tcp?

—
Reply to this email directly or view it on GitHub
#5 (comment).

from envy.

One of the reasons to avoid supporting this case is the confusion around how mounts/volumes work. Mounting the Docker socket should still work even when you run it remotely because Docker evaluates those paths on the host Docker runs on. If it doesn't work it's because your daemon is set to only listen on TCP, which if you decided to do that there's no reason to not also listen on the unix socket (you can have docker daemon listen multiple places).

from envy.

Maybe wait for orchestration to catch up? You could create new containers
and push them to remote servers etc. You have switch, how about clone and
later push. Anyway, envy is awesome and I haven't even had time to scratch
the surface for use cases. Thanks Jeff your work is really inspiring...
On 25 Jun 2015 20:22, "Jeff Lindsay" [email protected] wrote:

One of the reasons to avoid supporting this case is the confusion around
how mounts/volumes work. Mounting the Docker socket should still work even
when you run it remotely because Docker evaluates those paths on the host
Docker runs on. If it doesn't work it's because your daemon is set to only
listen on TCP, which if you decided to do that there's no reason to not
also listen on the unix socket (you can have docker daemon listen multiple
places).

—
Reply to this email directly or view it on GitHub
#5 (comment).

from envy.

Even if orchestration catches up I'm not sure I would even recommend it. I'm thinking more about clone/pull working with repos than direct instance to instance. Though I admit Docker should have always worked that way as well.

from envy.