Debugging Troubleshoot Docker Crashes from Beanstalk?

Question

I'm new to EB and AWS, and my docker images are building fine, but don't work on Elastic Beanstalk. My suspicion is that they do not connect to the database correctly, however I do not get anything useful when I run "eb logs" from the command line. Here are the errors:

{ "status": "FAILURE", "api_version": "1.0", "results": [ { "status": "FAILURE", "msg": "(TRUNCATED)...rrun.aws.json: No such file or directory 73927c49adff622a1a229d9369bdd80674d96d20f3eb99a9cdea786f4411a368 Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Wed May 20 17:15:02 UTC 2015:. Check snapshot logs for details. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/04run.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI", "returncode": 1, "events": [ { "msg": "Successfully pulled node:0.12.2-slim", "severity": "TRACE", "timestamp": 1432142064 }, { "msg": "Successfully built aws_beanstalk/staging-app", "severity": "TRACE", "timestamp": 1432142094 }, { "msg": "Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Wed May 20 17:15:02 UTC 2015:. Check snapshot logs for details.", "severity": "ERROR", "timestamp": 1432142102 } ] } ], "truncated": "true" } 

And after the assembly is completed:

 [2015-05-20T17:15:02.694Z] INFO [8603] - [CMD-AppDeploy/AppDeployStage0/AppDeployPreHook/04run.sh] : Activity execution failed, because: cat: /var/app/current/Dockerrun.aws.json: No such file or directory cat: /var/app/current/Dockerrun.aws.json: No such file or directory 73927c49adff622a1a229d9369bdd80674d96d20f3eb99a9cdea786f4411a368 Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Wed May 20 17:15:02 UTC 2015:. Check snapshot logs for details. (ElasticBeanstalk::ExternalInvocationError) caused by: cat: /var/app/current/Dockerrun.aws.json: No such file or directory cat: /var/app/current/Dockerrun.aws.json: No such file or directory 73927c49adff622a1a229d9369bdd80674d96d20f3eb99a9cdea786f4411a368 Docker container quit unexpectedly after launch: Docker container quit unexpectedly on Wed May 20 17:15:02 UTC 2015:. Check snapshot logs for details. (Executor::NonZeroExitStatus) 

Docker containers work locally, so what else can I do to understand what is happening? I keep hearing about the "snapshot logs", but where can I check these snapshot logs? Are they the result of me already running eb logs?

Answer 1

I had this problem when my containers failed because there was no traffic between EBS and RDS. If you use any database, try to collapse it. You can also try sudo docker logs CONTAINER_ID and try to catch something useful. Trying to start the container manually from the instance may also help. There is little chance that something will come.