2 Answers
- Newest
- Most votes
- Most comments
2
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
answered 3 years ago
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 vCPUs
with BlitzJS application ,timeoutSeconds:60 , intervalSeconds: 120,
0
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 "$@"
answered 2 years ago
Relevant content
- asked a year ago
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
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.