one more reason to use docker .
AWS EC2 Container Service
21–30 of 90 posts
Re: AWS EC2 Container Service
#22So 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]
The OP was referring to Linux Container Daemon LXD [1] which is built on top of LXC and promises to offer Docker-like features.
Re: AWS EC2 Container Service
#23Re: AWS EC2 Container Service
#24I'm disappointed that this requires an invite, particularly so close after Container Engine which I was able to try out immediately while still watching Cloud Platform Live the other day. Is 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.
Considering they've been tweeting about it [1] since before their competitors announced things I'd say it's unlikely to be a "response". It's far more likely that Docker has now been out long enough for the various providers to build services around it. AWS already had some docker support built in in April [2]. It's also pretty common to release services as previews. GCE lists theirs as an Alpha quality product.
[1] https://twitter.com/jeffbarr/status/529493907839533056
[2] http://blog.docker.com/2014/04/aws-elastic-beanstalk-launche...
Re: AWS EC2 Container Service
#25So 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]
Well, LXD doesn't actually exist yet, so Docker couldn't possibly be built on it.
You are likely confusing LXD with the present day LXC, which is understandable. You thinking that Docker is built on LXC is also understandable - but also not quite right.
Docker used LXC as the default container implementation for much of it's lifespan. However, it has since dropped LXC as the default and uses libcontainer instead.
The linux kernel does not actually specifically have a container implementation. Userland tools such as LXC ( https://linuxcontainers.org/ ) and libcontainer ( https://github.com/docker/libcontainer ) utilize things like kernel namespaces, cgroups, and a variety of other features to deliver the container experience.
Re: AWS EC2 Container Service
#26So 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]
No, Docker is not build on lxd. It used to be built on lxC, which is now an optional backend.
The grand-parent is correct that lxd is a newly introduced competitor to Docker.
I won't comment on whether it's good or bad, but it's an objective fact that canonical decided to reimplement what Docker does rather than contribute to it.
Re: AWS EC2 Container Service
#27Earlier quoted context omitted.
[deleted]
Docker is built on LXC, Linux containers. LXD is a new thing from Canonical, a hypervisor designed especially for containers that is supposed to guarantee hardware isolation.
> Docker is built on LXC, Linux containers
Nope, it currently defaults to libcontainer[1], not LXC, but through the use of execution drivers[2] you can still use LXC if you want to.
[1]: https://github.com/docker/libcontainer
[2]: http://blog.docker.com/2014/03/docker-0-9-introducing-execut...
Re: AWS EC2 Container Service
#28Re: AWS EC2 Container Service
#29I'm disappointed that this requires an invite, particularly so close after Container Engine which I was able to try out immediately while still watching Cloud Platform Live the other day. Is 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.
It's fairly typical. Though I usually get preview to any service reasonable fast just by clicking on their website.
E.g. Amazon Kinesis:
Preview 14 Nov 2013: http://aws.amazon.com/blogs/aws/amazon-kinesis-real-time-pro...
Got access less than week from that.
GA 16 Dec 2013: http://aws.amazon.com/about-aws/whats-new/2013/12/16/amazon-...
Re: AWS EC2 Container Service
#30Earlier 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.
Wasn't there just an AWS announcement yesterday about the ability to register VPC-private DNS records in Route 53? It screamed "SkyDNS competitor" to me but I couldn't figure out what Amazon wanted such a thing for. Makes sense now.