Hyper – Hypervisor-agnostic Docker engine

Re:Hyper – Hypervisor-agnostic Docker engine by kj92 on Thursday May 28, 2015 @10:08PM (#9622334)

Looks interesting. How is this different from Clear Container several days ago?

[ Parent | on HN ]

Re:Hyper – Hypervisor-agnostic Docker engine by tbronchain on Thursday May 28, 2015 @10:23PM (#9622364)

Hi there,

Thanks for your interest in Hyper!

We also noticed the release announcement of Clear Containers a few days ago. There are 2 main differences, the first being on the technology used, CC using RKT, while Hyper is based on Docker images. There is also a difference in term of philosophy, where Hyper aims to be a technology-neutral open source solution.

Hyper also have more features, such as running a Pod rather than one image on a hypervisor as a schedule unit.

For more details, please check our FAQ (https://hyper.sh/faq.html)

[ Parent | on HN ]

Re:Hyper – Hypervisor-agnostic Docker engine by philips on Friday May 29, 2015 @12:18AM (#9622623)

I don't feel this is correct. rkt can run docker images[1] and once the clear containers patches[2] land you will be able to run a docker image or an appc image inside of a VM under rkt.

[1] https://github.com/coreos/rkt/blob/master/Documentation/comm...

[2] https://github.com/coreos/rkt/pull/946

[ Parent | on HN ]

Re:Hyper – Hypervisor-agnostic Docker engine by josephjacks on Friday May 29, 2015 @12:03PM (#9625396)

I think the question was specifically in the context of CC.

[ Parent | on HN ]