# Container stuck activating

**URL:** <https://forums.suse.com/t/container-stuck-activating/7800>\
**Category:** Rancher 1.x\
**Created:** [November 15, 2017, 2:58pm UTC](https://forums.suse.com/t/container-stuck-activating/7800 "2017-11-15T14:58:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alessandro\_Degano](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alessandro_degano/32/3022_2.png) [@Alessandro\_Degano](https://forums.suse.com/u/Alessandro_Degano)\
**Post date:** [November 15, 2017, 2:58pm UTC](https://forums.suse.com/t/container-stuck-activating/7800/1 "2017-11-15T14:58:48Z")

</div>

Hello,  
I’ve a big image (~20gb) that takes couple of minute to launch when the container is created by docker run directly, although working fine after that.  
Also if I execute the same docker-compose I’m using on my private catalog in rancher I need to increase the COMPOSE\_HTTP\_TIMEOUT to 300 seconds, but again, a part from that works just fine.  
However when I launch the stack through the Rancher GUI I just get the service stuck in the status “activating”.  
Is there any parameter I can pass to rancher-compose.yml to mitigate the issue?

Thanks.