1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi, If I correctly understand your task are healthy before began the deployment. When you do the deployment the existing healthy tasks are been replaced with new ones that might have been some issue on starting the container. If the task are not able to start, the health check will keep display and unknown status as it didn't have time to gather the information on the new tasks. This could be the issue, but please provide more information to better understand the situation before and during the deployment. Please also have a look inside the Service into the "Deployment and Event" tab where you can find all the information related to your deployment and also some error logs with the issue that didn't allow you container to start
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa