# Failing to launch workers due to docker pull timeout

**URL:** <https://discuss.ray.io/t/failing-to-launch-workers-due-to-docker-pull-timeout/2332>\
**Category:** Ray Clusters\
**Created:** [May 29, 2021, 9:10pm UTC](https://discuss.ray.io/t/failing-to-launch-workers-due-to-docker-pull-timeout/2332 "2021-05-29T21:10:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yoav](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yoav/32/456_2.png) [@Yoav](https://discuss.ray.io/u/Yoav)\
**Post date:** [May 29, 2021, 9:10pm UTC](https://discuss.ray.io/t/failing-to-launch-workers-due-to-docker-pull-timeout/2332/1 "2021-05-29T21:10:09Z")

</div>

We recently moved to a larger docker image for the ray head and workers, and see many failures:

- head node often fails to start (“ray up” fails), the failure is often in the middle of the docker pull command (the returned error is “SSH command failed”.
- worker nodes started by the autoscaler are failing to get launched, again while pulling the docker, again with “SSH command failed”.

I suspect this is due to some timeout when running the ssh commands. I see the code has a default timeout of 120 seconds, how can I increase this default without changing ray code?