docker kill and capturing logs or buffers

So elasticbeanstalk when updating or changing a docker deployed image will use docker kill in order to terminate the running docker container in order to be able to switch it for the new container that it is going to stage.

I’d like to be able to capture the logging information from that container, but the container is sent a SIGKILL so I cannot directly have the container shutdown gracefully. I could hack the EB staging and deployment scripts to use docker stop instead of docker kill, but I’m confused why EB doesn’t give me the chance to clean up the app first before shutting it down.

  • Where to find my discourse output?
  • Docker EC2 & port binding
  • How do I pull Docker images from the Tutum private registry with Amazon ECS?
  • nodejs, docker, nginx and amazon aws deployment
  • docker dead but pidfile exists
  • Amazon ECS troobleshooting task start failures
  • I know it’s a long shot, but is there anyway I can hook around this in order to be able to capture this log output outside of constantly pushing it off the machine? I don’t really want to mess with amazon’s deployment scripts, but that seems like the only way to get this functionality. Anyone have any insight into this?

  • Load Hive data to elastic search stucks on 0% for map and reduce
  • Celery: worker receives first task after `broker_heartbeat` seconds
  • Linking container with docker-compose
  • Docker exits with a exit code on starting
  • Saving files on Mac OSX host to Docker container (auto-reloading)
  • Create a local end-to-end development environment
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.