weaveworks/ignite
Ignite a Firecracker microVM observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2709
- days_rel: n/a
- days_push: 1000
- n_releases_24m: 0
Adoption not part of the score
3529 stars · 233 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Weave Ignite is a VM manager that runs Firecracker microVMs from OCI/Docker images with a container-like UX and declarative GitOps management. It is now deprecated and no longer maintained, with Flintlock suggested as a successor.
Use cases
- run docker images as firecracker microvms
- boot lightweight vms in milliseconds from oci images
- manage fleets of vms declaratively with gitops
- replace docker run with vm isolation for untrusted workloads
- build vm images with docker build instead of qcow2 tooling
When to choose
- you need container-like ergonomics for firecracker microvms on linux with KVM
- you want to run OCI images as isolated VMs with fast boot times
When to avoid
- you need a maintained tool - the project is deprecated and unmaintained
- you are not on Linux with KVM available
- you need macOS or Windows host support
Facets
cli-tool · maturity abandoned
container-runtime deployment developer-tools cloud-computing infrastructure-as-code cli go firecracker microvm oci-images gitops kvm virtualization deprecated containers devops linux
1 source
- readme: https://github.com/weaveworks/ignite · fetched 2026-08-28 · 0ef9d6bd9175
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| weaveworks/ignite | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="weaveworks/ignite")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem