# Is it possible to use docker cli from another computer?

**URL:** <https://forums.suse.com/t/is-it-possible-to-use-docker-cli-from-another-computer/1699>\
**Category:** RancherOS\
**Created:** [February 11, 2016, 4:50pm UTC](https://forums.suse.com/t/is-it-possible-to-use-docker-cli-from-another-computer/1699 "2016-02-11T16:50:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johan\_Lindberg](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@Johan\_Lindberg](https://forums.suse.com/u/Johan_Lindberg)\
**Post date:** [February 11, 2016, 4:50pm UTC](https://forums.suse.com/t/is-it-possible-to-use-docker-cli-from-another-computer/1699/1 "2016-02-11T16:50:41Z")

</div>

Is it possible to run docker -H\<addresstomyranch-server/host from another computer?  
Im trying to get my builds from vs2015 deployed directly to my rancher. Before i have used the Dockertools for visual studio, but i cant get it to work when using rancher.  
From what i can tell there are no docker deamon listening on any port.

Or if anyone have other one click deployment routines I´m grateful for help.

-Edit  
By running docker daemon -H on my host i did get it to work.  
But it seems like after i ran the daemon i scrapped the agent. My host turned up as disconnected in rancher.  
After a reboot the server was found and my image was in place, although it doesn’t really seem the right way to deploy.  
Can i somehow enable the default daemon if any to listen on tcp while still working as intended?

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [February 11, 2016, 9:32pm UTC](https://forums.suse.com/t/is-it-possible-to-use-docker-cli-from-another-computer/1699/2 "2016-02-11T21:32:39Z")

</div>

Docker only listens on a local socket by default in most installations. You can configure it to accept remote connections, see: [https://docs.docker.com/engine/reference/commandline/daemon/#daemon-socket-option](https://docs.docker.com/engine/reference/commandline/daemon/#daemon-socket-option)

The Rancher agent uses the socket file, so you’d need something like `-H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375` . And make sure you read the parts about securing it, or you’re just opening up the equivalent of root to the outside world.

---

<div class="post-metadata">

**Author:** ![Johan\_Lindberg](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@Johan\_Lindberg](https://forums.suse.com/u/Johan_Lindberg)\
**Post date:** [February 11, 2016, 9:56pm UTC](https://forums.suse.com/t/is-it-possible-to-use-docker-cli-from-another-computer/1699/3 "2016-02-11T21:56:27Z")

</div>

Thanx,  
I totally missed it in the documentation.  
After following [http://docs.rancher.com/os/configuration/setting-up-docker-tls/](http://docs.rancher.com/os/configuration/setting-up-docker-tls/) it opened up fort secure connections on port 2376 which i could connect to after installing the client certs.

Now everything seems to work.

Extremely impressive tools, already have an service up with service link to an external db, scaleable .Net core api containers. And i believe im on good way setting up some node testing containers also. In one day with zero previous docker/rancher experience.  
And now one click deploy from VS2015. 🙂