amazon-ecs-agent

I still don't understand how this "Linux never breaks userland" thing holds up, it's been proven false. The 4.13 kernel introduced a change to effectively namespace sysctl settings (prevent the change from default from being copied to the host system into container processes). This broke any container runtimes that relied on host-wide sysctl settings. [1] https://github.com/aws/amazon-ecs-agent/issues/789 [2] https://success.docker.com/article/ipvs-connection-timeout-i...

Some container engines don't support the --init flag, such as Amazon ECS[0], so there is still a place for dumb-init and tini for the time being. [0] https://github.com/aws/amazon-ecs-agent/issues/852

(AWS employee here) First of all I can assure you that Amazon is 100% committed to containers. Amazon's compute strategy is aimed at three levels of abstraction: instances, containers, lambda. All three are equally important to Amazon. With regard to ECS feature set relative to K8, the thing to understand is that AWS follows a startup-like strategy of launching an MVP and then letting customer feedback drive roadmap from there. AWS is definitely not half hearted about ECS. Rather AWS is constantly working with customers to define a roadmap for further development on ECS. To me the most exciting thing about ECS is the open source work being done around ECS, for Blox (a framework for building out custom container scheduling logic), and the ECS agent itself: https://github.com/blox/blox https://github.com/aws/amazon-ecs-agent With these ECS

Not the OP, but I'd really like to be able to run containers with all unnecessary capabilities dropped: https://github.com/aws/amazon-ecs-agent/issues/223

You probably are aware, but AWS has a container orchestration service built into the platform with ECS. The container agent is open source (https://github.com/aws/amazon-ecs-agent). We're building an open-source platform at Convox that leverages ECS very successfully. https://github.com/convox/rack In my experience, ECS is easy to run, as it's a first class part of the platform. Boot up the right "cattle" AMIs with the right ASG configuration and you're good to go. K8, Docker Swarm, Mesos and Nomad have plenty of documented success but you to stand up and operate the orchestration layer yourself. This is booting up "pet" AMIs and making sure they are monitored, etc. Then you boot up your "cattle" AMIs to run your apps. The Convox philosophy is that you get application portability by packaging your app correctly with Docker. The orchestrat

Amazon Web Services | Seattle | Full Time | ONSITE The AWS Container Services team is hiring for a number of roles including engineers, managers, and product managers. The Container Services team at AWS owns Amazon EC2 Container Service (ECS) and Amazon EC2 Container Registry (Amazon ECR) and is tasked with enabling AWS customers and AWS service teams who want to build applications and services using Docker and other container technologies. Over the past few years, we have built a number of core systems designed to run and operate distributed applications built on top of Docker. We continue to enhance our platform by improving our existing systems and building new systems to solve our next set of problems and challenges. If you are interested in Linux, Docker, networking, building very large scale cluster management systems, schedulers,

We've been using EC2 Container Service for a few months now and at first glance it appears great but we've ran into quite a few problems using it: - You can only bind 1 port and 1 ELB to a service. This means, for example, if you have nginx listening on port 80 and 443 you need to manually configure the ELB and can't take advantage of automatically generated port numbers on the host (So you basically can only have 1 HTTP(s) server on a host) - There is no way to cleanly decommission a host from a cluster. Say if you want to reboot or replace a server in the cluster you can't tell ECS to drain connections from the ELB and move the containers off the host - Unable to specify rules for which hosts services should run on. For example you can't say that the service needs to make sure it has instances in X AZs or don't run multiple instances of

So this Amazon EC2 Container Service Agent[1] is the AWS's own equivalent of Google Cloud Platform's Kubernetes? (Granted, Kubernetes is platform agnostic.) [1]:https://github.com/aws/amazon-ecs-agent

Amazon EC2 Container Service - Full time, Seattle, WA We are hiring for a number of positions on the EC2 Container Service [1] team including software development managers [2], software development engineers [3], and web development engineers [4]. To date our focus has primarily been on building out a highly scalable set of backend services and distributed systems to manage and expose container and cluster state and for task scheduling. We are now looking to add engineers with a strong systems background, particularly around OS virtualization and networking. We are a growing team of (mostly) experienced engineers that likes to iterate quickly. We value scalability, operability, and security and expect everyone on the team to have a say in feature design and prioritization. We also have some fun open source projects [5]. If you are in