# Multimodal-workshop

**URL:** <https://forum.weaviate.io/t/multimodal-workshop/1292>\
**Category:** Support\
**Created:** [January 24, 2024, 12:10am UTC](https://forum.weaviate.io/t/multimodal-workshop/1292 "2024-01-24T00:10:51Z")\
**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:** [February 2, 2024, 12:05pm UTC](https://forum.weaviate.io/t/multimodal-workshop/1292/2 "2024-02-02T12:05:51Z")

</div>

hi @rsale really sorry for the delay here ☹

This os probably due to the fact that `multi2vec-bind` can take quite some time to be up and running.

One way to avoid this, is to make sure `multi2vec-bind` is running first, then spinning up Weaviate, like so

```auto
docker compose up -d multi2vec-bind

```

now you monitor the status of that cluster first, with `docker ps`

Once you are sure it is running, you can spin `docker compose up -d` again.

---

_[View the full topic](https://forum.weaviate.io/t/multimodal-workshop/1292)._