Container stuck activating

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?