# Failed while setting Multi node cluster using docker swarm on 2 VM

**URL:** <https://forum.weaviate.io/t/failed-while-setting-multi-node-cluster-using-docker-swarm-on-2-vm/1364>\
**Category:** Support\
**Created:** [February 3, 2024, 9:19am UTC](https://forum.weaviate.io/t/failed-while-setting-multi-node-cluster-using-docker-swarm-on-2-vm/1364 "2024-02-03T09:19:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [March 15, 2024, 2:14pm UTC](https://forum.weaviate.io/t/failed-while-setting-multi-node-cluster-using-docker-swarm-on-2-vm/1364/4 "2024-03-15T14:14:07Z")

</div>

Hi @fenglizzz !  
Check this thread for a complete example on multinode with docker compose:

> [@Docker Compose with multi node deployment issue](https://forum.weaviate.io/t/docker-compose-with-multi-node-deployment-issue/1720/2):
>
> Hi @fenglizzz !! Welcome to our community hugs It’s not a good idea to reference the CLUSTER\_JOIN by IPs (or any container to container connection inside docker/k8s to be fair), as those will eventually change down the road, or maybe even after a reboot. Here are some steps to get this party going. partying_face First, let’s create a docker attachable network: docker network create --attachable weaviate Now, using the [latest docker compose](https://weaviate.io/developers/weaviate/installation/docker-compose#sample-docker-compose-file), and using this doc to [adjust it to a multi nod…](https://weaviate.io/developers/weaviate/installation/docker-compose#multi-node-setup)

---

_[View the full topic](https://forum.weaviate.io/t/failed-while-setting-multi-node-cluster-using-docker-swarm-on-2-vm/1364)._