AWS ElasticBeanstalk: o contêiner continua reiniciando

Question

Estou tentando implantar um cluster Elastic Beanstalk do Docker de vários contêineres na AWS e minha situação é:

• Eu tenho 7 contêineres docker, seis dos quais são aplicativos Scala cada escutando na porta 9000 para o tráfego HTTP.
• O primeiro contêiner é um Recipiente nginx-proxy que apenas faz um proxy_pass para o outro recipientes.

O que estou vendo é bastante estranho e não consigo saber onde ajustar isso de qualquer maneira - meus contêineres parecem estar começando corretamente, mas de alguma forma, a inicialização deles é interrompida por algo e todos os contêineres são contados para reiniciar.

Veja como é o log do culpado;

-------------------------------------
/var/log/containers/centralapp-core-867cf4f2655c-stdouterr.log
-------------------------------------
Play server process ID is 1
[[37minfo[0m] play - database [default] connected at jdbc:mysql://some-mysql-server/somedb-core?characterEncoding=UTF-8
[DEBUG] [09/23/2015 16:30:25.591] [main] [EventStream(akka://application)] logger log1-Logging$DefaultLogger started
[DEBUG] [09/23/2015 16:30:25.593] [main] [EventStream(akka://application)] Default Loggers started



-------------------------------------
/var/log/containers/centralapp-push-play-697ba6e223db-stdouterr.log
-------------------------------------
Play server process ID is 1
[[37minfo[0m] play - database [default] connected at jdbc:mysql://some-mysql-server/somedb-push?characterEncoding=UTF-8
[[37minfo[0m] application - Push system starting at 2015-09-23T16:39:33.223Z
[INFO] [09/23/2015 16:39:34.582] [main] [Remoting] Starting remoting
[INFO] [09/23/2015 16:39:35.186] [main] [Remoting] Remoting started; listening on addresses :[akka.tcp://[email protected]:2552]
[INFO] [09/23/2015 16:39:35.196] [main] [Remoting] Remoting now listens on addresses: [akka.tcp://[email protected]:2552]
[[37minfo[0m] play - Starting application default Akka system.
[[37minfo[0m] application - OK: Actor[akka://application/user/PushMaster#-733988473]
[[37minfo[0m] play - Application started (Prod)
[[37minfo[0m] play - Listening for HTTP on /0:0:0:0:0:0:0:0:9000
[[37minfo[0m] play - Shutdown application default Akka system.
[INFO] [09/23/2015 16:39:39.307] [application-akka.remote.default-remote-dispatcher-14] [akka.tcp://[email protected]:2552/system/remoting-terminator] Shutting down remote daemon.
[INFO] [09/23/2015 16:39:39.310] [application-akka.remote.default-remote-dispatcher-14] [akka.tcp://[email protected]:2552/system/remoting-terminator] Remote daemon shut down; proceeding with flushing remote transports.
[INFO] [09/23/2015 16:39:39.367] [ForkJoinPool-3-worker-3] [Remoting] Remoting shut down
[INFO] [09/23/2015 16:39:39.368] [application-akka.remote.default-remote-dispatcher-14] [akka.tcp://[email protected]:2552/system/remoting-terminator] Remoting shut down.



-------------------------------------
/var/log/containers/centralapp-core-48fc5c7201d9-stdouterr.log
-------------------------------------
Play server process ID is 1
[[37minfo[0m] play - database [default] connected at jdbc:mysql://some-mysql-server/somedb-core?characterEncoding=UTF-8
[DEBUG] [09/23/2015 16:30:03.712] [main] [EventStream(akka://application)] logger log1-Logging$DefaultLogger started
[DEBUG] [09/23/2015 16:30:03.713] [main] [EventStream(akka://application)] Default Loggers started

• é onde o log termina.

Parece que algo faz o EB pensar que a implementação falhou e tenta reimplantar tudo.

Qual pode ser a razão por trás disso?

Obrigado.