firebuild
undocker
firebuild | undocker | |
---|---|---|
5 | 2 | |
92 | 303 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | over 1 year ago | |
Go | Python | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
firebuild
-
We clone a running VM in 2 seconds
Regarding turning Dockerfiles into a MicroVM: https://gruchalski.com/posts/2021-03-23-introducing-firebuil..., on GitHub: https://github.com/combust-labs/firebuild. This could get you started.
Disclaimer: I’m the author.
-
Podman 4.0.0
> See, and in almost all of my use-cases, I really do. I do HPC computing, which is almost always a multi-tenant environment.
Maybe you need firecracker with something along the lines of https://github.com/combust-labs/firebuild?
-
Hypervisor for multi-tenant computing, like it should be
I was the one who posted that question and I deleted it because I understood I was asking to compare apple to oranges. Firecracker uses KVM under the hood. With regards to the overhead, sure, there's going to be resources needed but firecracker is pretty good at running VMs will low level overhead. We're talking thousands on a single host.
I've done some fair share of evaluating firecracker for https://github.com/combust-labs/firebuild and the need to provision is red herring. firebuild can run a VM directly from a Dockerfile and Docker image. Fly.io team does something similar. It's basically a fully functional app out of the container within a matter of milliseconds.
What would be nice is to see a direct comparison between your solution and firecracker.
-
Docker Without Docker
I am working on something like this: https://github.com/combust-labs/firebuild.
From a Dockerfile, it's not as simple without creating an image first.
undocker
- How can I open a docker image
-
We clone a running VM in 2 seconds
- you can then get a list of the tarballs in this image by extracting this tarball and reading the file `manifest.json`; `Config` -> `Layers` will give you a list of tarballs (see undocker for how to do this: https://github.com/larsks/undocker)
What are some alternatives?
cloud-hypervisor - A Virtual Machine Monitor for modern Cloud workloads. Features include CPU, memory and device hotplug, support for running Windows and Linux guests, device offload with vhost-user and a minimal compact footprint. Written in Rust with a strong focus on security.
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
linuxkit - A toolkit for building secure, portable and lean operating systems for containers
firecracker-go-sdk - An SDK in Go for the Firecracker microVM API
firecracker-containerd - firecracker-containerd enables containerd to manage containers as Firecracker microVMs
mariadb-podman-socket-activation - Demo of a templated systemd user service that runs rootless Podman and starts MariaDB with socket activation
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
kubevirt - Kubernetes Virtualization API and runtime in order to define and manage virtual machines.
actuated - Blazingly fast CI runners
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
dive - A tool for exploring each layer in a docker image