Anyone have any insight about if this handles service discovery? It claims "cluster management" which usually means discovery, but there is no mention of it. Maybe Amazon is expecting you to handle that?
AWS EC2 Container Service
11–20 of 90 posts
Re: AWS EC2 Container Service
#12Re: AWS EC2 Container Service
#13Anyone have any insight about if this handles service discovery? It claims "cluster management" which usually means discovery, but there is no mention of it. Maybe Amazon is expecting you to handle that?
From: https://aws.amazon.com/ecs/details/ ...including the Docker repository and image, memory and CPU requirements, and how the containers are linked to each other. You can launch as many tasks as you want from a single task definition file that you can register with the service. Very few details but it looks like container lifting across hosts. If so this is great news.
Re: AWS EC2 Container Service
#14Is this typical for new AWS offerings?
It makes me wonder if it's something that truly isn't ready for prime time, but is being rushed / forced by the mounting Docker hype and GKE announcement.
Re: AWS EC2 Container Service
#15Re: AWS EC2 Container Service
#16Earlier quoted context omitted.
From: https://aws.amazon.com/ecs/details/ ...including the Docker repository and image, memory and CPU requirements, and how the containers are linked to each other. You can launch as many tasks as you want from a single task definition file that you can register with the service. Very few details but it looks like container lifting across hosts. If so this is great news.
Yes but there are a lot of ways that "the containers are linked together" could be implemented and some of them e.g. key value store require modifying application code quite a bit whereas e.g. DNS does not.
Re: AWS EC2 Container Service
#17So Azure, GCE, and now EC2 all support docker natively. Sorry Canonical and LXD, but docker has basically won at this point. There simply isn't a good reason to "compete" when you can just add features to docker at this point.
Re: AWS EC2 Container Service
#18Security-wise, if I understand correctly, this is a very interesting offering. 1. The containers live on "your" VMs so you get the isolation of a virtual machine and do not worry about the other tenants' containers. 2. The VMs are part of a "private cloud", i.e., the internal network is not accessible by other tenants' VMs and containers. #2 is what worried me the most in other container service offerings. It's easy…
Re: AWS EC2 Container Service
#19So Azure, GCE, and now EC2 all support docker natively. Sorry Canonical and LXD, but docker has basically won at this point. There simply isn't a good reason to "compete" when you can just add features to docker at this point.
[deleted]
LXD is a new thing from Canonical, a hypervisor designed especially for containers that is supposed to guarantee hardware isolation.
Re: AWS EC2 Container Service
#20So Azure, GCE, and now EC2 all support docker natively. Sorry Canonical and LXD, but docker has basically won at this point. There simply isn't a good reason to "compete" when you can just add features to docker at this point.
[deleted]
Note that there isn't really a Linux kernel feature called LXC. The LXC userspace just ties all of the namespacing and cgroup functionality into 1 coherent super-chroot style environment. That is the same as docker does with libcontainer.