hyperhq

runv

Go2015–2021

hyperhq / runv · Archived

runv

Hypervisor-based Runtime for OCI

Systems & Infrastructure Languages & Compilers

Explore on GitHub Read Hacker News discussions

11Distinct people

14Mentions

0Explicit recommenders

828GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Hypervisor-based Runtime for OCI

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2015-09-24 10:30:08 UTC to 2021-09-01 01:43:51 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	0	1
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	4	1	3
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	5	0	5
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	1	0	1

What Hacker News says

14 sources

grawlinson·Sep 1, 2021

Arch packager here, looks like this can't realistically be packaged due to a dependency (runv[0]) being deprecated at it's upstream source. A lot of these container runtimes are needlessly complicated and not very enjoyable to package, so this is why not many are available in the official repositories. [0]:https://github.com/hyperhq/runv

In Ask HN: Any Good Alternative for Docker?

yjftsjthsd-h·Dec 17, 2020

You can do that in docker by using https://github.com/hyperhq/runv

In 51% of 4M Docker images have critical vulnerabilities

hardwaresofton·Jul 11, 2018

Note that clear containers the runtime has been replaced by kata-containers[0], which is a merge with runv[1]. [0]: https://github.com/kata-containers [1]: https://github.com/hyperhq/runv

In Runq – Runc-based runtime to run regular Docker images in KVM/Qemu

hardwaresofton·Apr 3, 2018

I think this is how I most commonly recognize someone that is familiar with lxc +/- docker and containerization in general. A firm grasp of the fact that they're just beefy processes, isolated wiht namespaces and cgroups is the best, most succint way to describe docker (without even mentioning the benefits), but it also requires that the hearer knows what namespaces and cgroups are. If I had to rank understanding in explanations of docker: 1. "Makes your application really portable"/other explanations that only cover the benefits of docker not how it works 2. "Lightweight VMs" 3. "LXC + some other stuff" 4. "processes + namespaces + cgroups (+/- image management tools, etc)" 100% agreed on the point you made, pretty sure docker+swarm and other orchestration efforts have basically lost the competition. Kubernetes just has the mind share, a

Read the rest

nd even better than that -- it's actually good. Kubernetes also has multiple competing container runtimes all rushing to fit the CRI (Container Runtime Interface). Just some of the stuff out there: * cri-containerd - https://github.com/containerd/cri-containerd * runv (hypervisor based) - https://github.com/hyperhq/runv * clear containers (hypervisor based) - https://github.com/clearcontainers/runtime * kata containers (hypervisor based, collaboration of runv + clear container) - https://katacontainers.io/ * frakti (combination of runv & docker, enabling switching @ runtime) - https://github.com/kubernetes/frakti A bunch of the projects are in their infancy, but the CNCF/kubernetes and the community are doing the right thing investing in lots of them, and letting the good ones bubble to the top. I don't run a production kubernetes cluster but I've found cri-containerd to be really easy to use and haven't had any major problems with it, mostly small configuration things. The last one, frakti, gets me really excited, because it lets you be flexible about which containers run in more protected environments and which don't. Also really exciting is frakti v2 (https://github.com/kubernetes/frakti/tree/containerd-kata), which is kata + containerd.

In A Workshop on Linux Containers: Rebuild Docker from Scratch

tilpner·Nov 1, 2017

An example for such an alternative backend would be runv, which can apparently be used with Docker (though I couldn't get it to work well, but that was probably just my fault) https://github.com/hyperhq/runv#run-it-with-docker

In LightVM – A new virtualization solution based on Xen

gnepzhao·Jul 26, 2017

github.com/hyperhq/runv

In Azure Container Instances

gnarmis·Jul 26, 2017

But Hyper.sh is still competitive, I think, even though it's super young. They already have a high level AWS Lambda alternative (Hyper Func) that uses containers and is fully language agnostic, and they have reasonable pricing-per-minute figured out. They also have open sourced their tech [1], so for certain companies they probably are compelling. Perhaps they should provide the kind of ease-of-use on top of the stuff they already provide that will cut open a steady market for them, like a Heroku but with this underlying tech and thus more dynamic on scaling and flexible on tech stack. [1] https://github.com/hyperhq/runv is one example

In Azure Container Instances

nogox·Jun 30, 2017

Did you try runV. It launches a Docker image into a micro VM in 100ms. github.com/hyperhq/runv

In Container Isolation Gone Wrong

XorNot·Jan 31, 2017

Lately I've been sending a bunch of patches upstream to the runv project (https://github.com/hyperhq/runv). Turns out that wrapping the docker interface with full VM isolation is a model I very much like.

In What's new in Docker 1.13: prune, secrets, checkpoints and more

activatedgeek·Dec 3, 2016Submission

runV: Hypervisor-Based Runtime for OCI

1 points · Open discussion

XorNot·Nov 6, 2016

In my context it's because big data became a thing. Nobody wants to pay the virtualization IO overheads anymore. That said, I've found myself swinging back towards preferring VMs - with docker-like infrastructure made available. The runv project (https://github.com/hyperhq/runv/) is an interesting and functional take on Docker-with-VMs since I spend way too much time wanting to do privileged things in containers.

In Docker in Production: A retort

aplanas·Nov 4, 2016

I like the initial idea very much. As I can see this is a wrapper over QEMU and controlled by QMP [1][2], so they are providing a kernel, initrd and a image. It is also configuring a machine profile (memory, vcpu, bus, devices, etc.). There are also interfaces for libvirt, xen and others virtualization technologies. This also looks similar of what Docker is doing now in Windows with HyperV. My question here is: from where comes the speed improvement in relation with a classical VM approach? [1] https://github.com/hyperhq/runv/blob/master/hypervisor/qemu/... [2] https://github.com/hyperhq/runv/blob/master/hypervisor/qemu/...

In Hyper Is Docker Done the Right Way

resouer·May 25, 2016

And another different side of HyperContainer is that it follows OCI spec, check the runv project here: https://github.com/hyperhq/runv/, so technically speaking, it's a hypervisor version of OCI, just like docker is a linux container version of OCI. Seems rkt/clear linux or LXD does not.

In Hypernetes: Bringing Security and Multi-Tenancy to Kubernetes

nogox·Sep 24, 2015

Check www.hyper.sh and https://github.com/hyperhq/runv They can boot a new VM with Docker images in 200ms, which is very close to LXC, and perfectly isolated by hypervisor. The problem of "Virtual Machine" is not "Virtual"/Virtualization, the problem is the full blown guest OS, aka "Machine".

In Don't expose the docker socket, even to a container