# How to deploy to two machines？

**URL:** <https://forum.weaviate.io/t/how-to-deploy-to-two-machines/743>\
**Category:** Support\
**Created:** [September 27, 2023, 3:54am UTC](https://forum.weaviate.io/t/how-to-deploy-to-two-machines/743 "2023-09-27T03:54:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [September 27, 2023, 12:33pm UTC](https://forum.weaviate.io/t/how-to-deploy-to-two-machines/743/2 "2023-09-27T12:33:01Z")

</div>

Hi @chris_hoo !

I believe the problem is that those two containers might not be able to consistently communicate with each other.

while using docker, you should avoid using IPs, as those are subject to be changed.

I believe you have seen this post (saw you comment there):

> [@Can only Docker Compose be used for multi node deployment?](https://forum.weaviate.io/t/can-only-docker-compose-be-used-for-multi-node-deployment/517/2):
>
> Hi @codehelen ! Welcome to our community slight_smile This must be some networking issue along the way, as your docker is correct (see below) A starting point is making sure that weaviate-node2-IP can communicate with weaviate-node1-IP on all specified ports. A good example on how to run with ad-hoc containers (at the same docker host): First, create a docker attachable network docker network create weaviate --atachable note that weaviate, above, can be whatever network name you want. Mak…

Where you able to use it?

---

_[View the full topic](https://forum.weaviate.io/t/how-to-deploy-to-two-machines/743)._