# Odd behavior with Ray cluster setup with Docker

**URL:** <https://discuss.ray.io/t/odd-behavior-with-ray-cluster-setup-with-docker/10213>\
**Category:** Ray Core\
**Created:** [April 13, 2023, 4:17am UTC](https://discuss.ray.io/t/odd-behavior-with-ray-cluster-setup-with-docker/10213 "2023-04-13T04:17:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marsupialtail](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/marsupialtail/32/1950_2.png) [@marsupialtail](https://discuss.ray.io/u/marsupialtail)\
**Post date:** [April 13, 2023, 4:17am UTC](https://discuss.ray.io/t/odd-behavior-with-ray-cluster-setup-with-docker/10213/1 "2023-04-13T04:17:38Z")

</div>

**How severe does this issue affect your experience of using Ray?**

- Medium: It contributes to significant difficulty to complete my task, but I can work around it.

I have been trying to use the Ray cluster yaml interface to spin up Ray clusters.

I’ve noticed that when the ray up command finishes, the workers just get started and are not connected to the head node. As a result if you immediately log on to the head node and start querying cluster\_resources() you are not going to see the worker nodes. Is this expected behavior?

As a start, it would be great to let me know _when_ the workers have finished setting up their setup commands.