Alex Zenla 15efce38cc fix(build): use host resolv.conf in os build chroot
The resolv.conf that the stage1 os script generates is fine for actual use,
but our GitHub workflows now uses the Step Security hardened runner action.
This action replaces the nameserver so that all lookups go through that,
but because the chroot calls apk add, it needs to contact the internet.
On the GitHub workflows, the OS build currently fails since the hardened
runner cannot access other nameservers.
2024-05-16 05:15:13 +00:00
2024-03-10 00:22:24 +00:00
2024-03-08 08:12:10 +00:00
2024-04-23 09:41:56 +00:00
2024-03-22 04:41:38 +00:00
2024-05-10 01:44:42 +00:00
2024-03-08 08:12:10 +00:00
2024-03-13 11:38:14 +00:00
2024-04-02 20:17:34 +00:00

krata

The Edera Hypervisor

license discord check nightly


Introduction

krata is a single-host hypervisor service built for OCI-compliant containers. It isolates containers using a type-1 hypervisor, providing workload isolation that can exceed the security level of KVM-based OCI-compliant runtimes.

krata utilizes the core of the Xen hypervisor, with a fully memory-safe Rust control plane to bring Xen tooling into a new secure era.

Hardware Support

Architecture Completion Level Virtualization Technology
x86_64 100% Completed Intel VT-x, AMD-V
aarch64 30% Completed AArch64 virtualization
Description
Mirror of Krata Hypervisor
Readme GPL-2.0 9.3 MiB
Languages
Rust 98.1%
Shell 1.9%