Github messages for voidlinux
 help / color / mirror / Atom feed
From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: ignite (& firecracker-microvm)
Date: Wed, 22 Jun 2022 06:24:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37638@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

New issue by Animeshz on void-packages repository

https://github.com/void-linux/void-packages/issues/37638

Description:
### Package name

ignite

### Package homepage

https://github.com/weaveworks/ignite

### Description

Weave Ignite is an open source Virtual Machine (VM) manager with a container UX and built-in GitOps management.

It combines [Firecracker MicroVMs](https://aws.amazon.com/about-aws/whats-new/2018/11/firecracker-lightweight-virtualization-for-serverless-computing/) with Docker / [OCI images](https://github.com/opencontainers/image-spec) to unify containers and VMs.

That is, kind of a hybrid instance of docker and firecracker-microvm where control is exactly like docker (build process and run process) yet there can be a kernel and init at runtime just like any other VM, you can access hardware devices, iptables and many more. Firecracker also provides [jailer](https://github.com/firecracker-microvm/firecracker/blob/main/docs/jailer.md) which deals with adding restrictions and limiting resources to the vm. The MicroVM also boots up in [quater of a second](https://gist.github.com/sameo/0647d6aaa36e73e6b536b51c29db1ead).

### Does the requested package meet the quality requirements?

System

### Is the requested package released?

Yes

                 reply	other threads:[~2022-06-22  4:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37638@inbox.vuxu.org \
    --to=animeshz@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).