- 新しい順
- 投票が多い順
- コメントが多い順
There are two things worth trying:
- Adjust the logging on the containers you're trying to deploy. The logs that you see on Lightsail are the same as the logs from the containers themselves (Lightsail just adds a couple logs about deployment status), so if you're not getting enough information, you need to log more from your containers.
- Adjust your healthcheck settings. Some containers take longer than the default settings to become healthy. You can adjust your healthcheck settings when you create a deployment. https://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/API_ContainerServiceHealthCheckConfig.html
I'm facing the same problem. Even redeploying of already worked container service causes the "Took too long". It has nothing to do with logging or health check settings because a service/container simply does not run.
Adjust healthcheck settings does the trick, In my case, I am using
1 GB RAM, 0.5 vCPUswith BlitzJS application ,timeoutSeconds:60 , intervalSeconds: 120,
I went through this problem, your application is taking a long time to start, in my case it is a large application in spring boot. To solve it you have to increase the processing of your cluster, I was increased and testing, when I reached that 1 GB RAM, 0.5 vCPUs worked.
I resolved this issue by adding CMD command inside my lauch script. Since my container was running php-fpm I added this code at the end of launch script
set -- php-fpm "$@"
exec "$@"
Region: eu-north-1
I can't even roll back to a previous working deployment - same issue..
I am having the same issue trying to Deploy a spring-boot app docker image. Set the timeout to 120 via CLI, deployment states to be finished after a few seconds, but finally fails after 120 secs with: deployment:12 took too long.
How did you solve it?
Hi, have any progress? I'm facing the same problem and recommendation in answer definitely can't work.