Hyper Is Docker Done the Right Way
thenewstack.io
Hyper Is Docker Done the Right Way
1–10 of 37 posts
Re: Hyper Is Docker Done the Right Way
#2Is this not what ECS aims to do?
Re: Hyper Is Docker Done the Right Way
#3Is this not what ECS aims to do?
The difference between Hyper and ECS is that ECS (and Docker Cloud, and GCE) all require that you provision and manage your own Docker server cluster.
With Hyper this is abstracted away which has a few benefits. Hyper also runs on HyperContainers (https://docs.hypercontainer.io/) which provides secure (VM like) multi-tenancy with container agility.
Re: Hyper Is Docker Done the Right Way
#4Is this not what ECS aims to do?
The difference between Hyper and ECS is that ECS (and Docker Cloud, and GCE) all require that you provision and manage your own Docker server cluster. With Hyper this is abstracted away which has a few benefits. Hyper also runs on HyperContainers ( https://docs.hypercontainer.io/ ) which provides secure (VM like) multi-tenancy with container agility.
Excuse me for my ignorance, but what does "container agility" mean?
Re: Hyper Is Docker Done the Right Way
#5Other than using the Docker format / API, how is this not just a variant VM deployment strategy?
If every container is running its own kernel on a hypervisor, doesn't this eliminate one of the key benefits of a true Container system, the kernel/memory overhead?
Re: Hyper Is Docker Done the Right Way
#6> "CoreOS, DigitalOcean, and Docker are sponsors of The New Stack."
Interesting and somewhat funny
Re: Hyper Is Docker Done the Right Way
#7Other than using the Docker format / API, how is this not just a variant VM deployment strategy? If every container is running its own kernel on a hypervisor, doesn't this eliminate one of the key benefits of a true Container system, the kernel/memory overhead?
What overhead?
Re: Hyper Is Docker Done the Right Way
#8Earlier quoted context omitted.
The difference between Hyper and ECS is that ECS (and Docker Cloud, and GCE) all require that you provision and manage your own Docker server cluster. With Hyper this is abstracted away which has a few benefits. Hyper also runs on HyperContainers ( https://docs.hypercontainer.io/ ) which provides secure (VM like) multi-tenancy with container agility.
Excuse me for my ignorance, but what does "container agility" mean?
He was talking about the boot speed, and the push/pull image workflow.
Re: Hyper Is Docker Done the Right Way
#9Other than using the Docker format / API, how is this not just a variant VM deployment strategy? If every container is running its own kernel on a hypervisor, doesn't this eliminate one of the key benefits of a true Container system, the kernel/memory overhead?
What overhead?
The benefit of a container over a full VM is meant to be that the container scheme has just one kernel running.
This scheme would effectively be just one container per VM, thus negating the benefit.
(Edit: So.. it would appear that the benefit is that they're read-only-sharing the kernel between VMs)
Re: Hyper Is Docker Done the Right Way
#10Other than using the Docker format / API, how is this not just a variant VM deployment strategy? If every container is running its own kernel on a hypervisor, doesn't this eliminate one of the key benefits of a true Container system, the kernel/memory overhead?
With HyperContainer, we make the performance/overhead of virtualized container similar to linux container --- 130ms launch time, and sharing the read-only part of memory (kernel and init). As a result, we can use it as a more secure container.