1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
A Docker engine timeout settings in backend code as “const (defaultCommandTimeout = 300)”. The aws:elasticbeanstalk:command timeout option (Timeout config in Console, default is 600s) is in fact applied. Nevertheless, this applies for the whole Beanstalk deployment. The commands during building Docker app are timing out before and failing. The 300 seconds timeout is fixed and cannot be modified at the moment.
Please create a support case to AWS with below information that helps AWS support team to provide work around if available.
- A time frame when the issue appears.
- Upload failed log files.
- Dockerfile / docker-compose.yaml / Dockerrun.aws .json files
- The size of the image you would like to pull from ECR, also cloud you please kindly provide some context of the image if it’s with a large size.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 8 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 mesi fa
- AWS UFFICIALEAggiornata 9 mesi fa