andyshinn

  Location: Austin, TX
  Remote: Yes
  Willing to relocate: No
  Technologies: Terraform, Ansible, AWS, Datadog, Containers, Linux, Python
  Résumé/CV: http://linkedin.com/in/andyshinn/
  Email: andys@andyshinn.as

https://news.ycombinator.com/item?id=9674982

I've been doing stuff with Docker for a while and I have run in to issues here and there, but never the PID reaping problem. In fact, I actually strive now to make the application PID 1 and only run 1 process. This is specifically so that the container will exit and the host or other scheduling logic can deal with the event.

I already asked a question on another site. But I'll ask some more here:

* Will this at (least the scheduler / scaler component) be open source? * Any plans to scale the EC2 instances as well (scaling containers is great, but I usually need to scale out more CPU and memory as well)?

It is really exciting to watch the evolution of Deis. Been following since around 0.8. I value the way you guys interact with the community and hope projects like this continue to help shape the way we use containers.

The Docker Hub does also have a mode called "Automated Builds" which will pull down the repository, build an image based on the Dockerfile and push it. However, you do have to pick one or the other (you cannot push your own image to a repository configured as an Automated Build).

It is their own nginx HTTP / TCP router, which is backed by etcd and confd. You can check it out at https://github.com/deis/deis/tree/master/router. Essentially, you can fire up multiple of these instances, and Deis uses them to route application, controller, and git traffic to the proper container.