# Rancher HA and docker-machine

**URL:** <https://forums.suse.com/t/rancher-ha-and-docker-machine/3074>\
**Category:** Rancher 1.x\
**Created:** [June 9, 2016, 3:09pm UTC](https://forums.suse.com/t/rancher-ha-and-docker-machine/3074 "2016-06-09T15:09:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rainchild19](https://avatars.discourse-cdn.com/v4/letter/r/ecc23a/32.png) [@rainchild19](https://forums.suse.com/u/rainchild19)\
**Post date:** [June 9, 2016, 3:09pm UTC](https://forums.suse.com/t/rancher-ha-and-docker-machine/3074/1 "2016-06-09T15:09:18Z")

</div>

Hi,

I was trying to set up Rancher HA and was using digital ocean as my cloud provider. Typically I use docker-machine to create my droplet, via something like:

docker-machine -D create   
–driver digitalocean   
–digitalocean-access-token=xxxxx   
–digitalocean-image=docker   
–digitalocean-region=nyc3   
–digitalocean-size=4gb   
–digitalocean-ipv6=false   
–digitalocean-private-networking=true   
–digitalocean-backups=false   
RANCHER1

I did notice that docker-machine automatically starts the docker-daemon on port 2376 which gives a port conflict when starting the [rancher-ha.sh](http://rancher-ha.sh) scripts. I was curious to know if there was any best practices around avoiding this as I can see issues if anyone is using docker-machine to initially create their VM host.

Note, I was able to get around this issue by creating the droplet via the UI, just wondering if there was another way around the issue.

Thanks!

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [June 20, 2016, 6:06pm UTC](https://forums.suse.com/t/rancher-ha-and-docker-machine/3074/2 "2016-06-20T18:06:05Z")

</div>

It’d be great if you created a ticket in github so we can look into it.