cosmic-comp
kata-containers
cosmic-comp | kata-containers | |
---|---|---|
16 | 11 | |
392 | 4,922 | |
5.6% | 3.1% | |
9.7 | 10.0 | |
5 days ago | 4 days ago | |
Rust | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
cosmic-comp
- Maestro: A Linux-compatible kernel in Rust
-
Making a Wayland Compositor and WM using Rust
Maybe take a look at cosmic-comp it is currently in development by System76 for their own Cosmic DE. Smithay also has Anvil and Smallvil contained in it's repository, both are example implementations of a compositor using Smithay.
- Functional programming
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
cosmic-comp
-
Is the new Cosmic DE going to improve stability, performance and especially BATTERY on pop OS?
COSMIC DE isn't a singular thing, it's a project of several smaller projects being built on top of each other, like the cosmic-text project that'll be used for font rendering and this new cosmic-comp UI compositor project.
-
Rust in industry
we have a lot of Rust projects of different scopes, but I am mostly working on cosmic-comp, a wayland compositor for our new upcoming Linux Desktop Environment. All Open-Source: https://github.com/pop-os/cosmic-comp
-
Will the Pop_OS Cosmic Desktop environment support Wayland?
Thanks for the reply /u/mmstick. Also, would you know what causes this issue: https://github.com/pop-os/cosmic-comp/issues/28 I keep running into it when trying to compile cosmic-epoch
-
pop os cosmic window manager
See https://github.com/pop-os/cosmic-comp
-
COSMIC Panel First Look
We hired the talent behind smithay, and cosmic-comp is based on it, which has been developed to the point where we have an early prototype with some functioning wayland-shell applets.
- Exploring System76's New Rust Based Desktop Environment
kata-containers
- Maestro: A Linux-compatible kernel in Rust
-
Fly Kubernetes
Seems like Fly.io Machines are trying reimplement Kata Containers with the Firecracker backend [0].
Kata has a guest image and guest agent to run multiple isolated containers [1].
[0] https://katacontainers.io/
[1] https://github.com/kata-containers/kata-containers/blob/main...
-
Kata Containers: Virtual Machines (VMs) that feel and perform like containers
> Last time I looked (a few months ago), the documentation was pretty sparse or outdated.
It still is, though it works somewhat seamlessly when installing with https://github.com/kata-containers/kata-containers/blob/main...
Though only one of the hypervisors works well.
-
Method to block possible internet traffic from LLaMA on MacOS
Better to use a secure VM, can even get container-like VMs with kata-containers
-
Kata Containers vs gVisor?
As I understand,Kata Containers
-
Firecracker MicroVMs
Kubernetes using Kata containers as a containerd backend
https://github.com/kata-containers/kata-containers/blob/main...
-
Container security best practices: Ultimate guide
My home k8s cluster is now "locked down" using micro-vms (kata-containers[0]), pod level firewalling (cilium[1]), permission-limited container users, and mostly immutable environments. Given how quickly I rolled this out; the tools to enhance cluster environment security seem more accessible now than my previous research a few years ago.
I know it's not exactly a production setup, but I really do feel that it's the most secure runtime environment I've ever had accessible at home. Probably more so than my desktops, which you could argue undermines most of my effort, but I like to think I'm pretty careful.
In the beginning I was very skeptical, but being able to just build a docker/OCI image and then manage its relationships with other services with "one pane of glass" that I can commit to git is so much simpler to me than my previous workflows. My previous setup involved messing with a bunch of tools like packer, cloud-init, terraform, ansible, libvirt, whatever firewall frontend was on the OS, and occasionally sshing in for anything not covered.
[0] https://github.com/kata-containers/kata-containers
-
Docker Without Docker
I'm really impressed by fly.io, and the candidness with which they share some of their really awesome technology. Being container-first is the next step for PaaS IMO and they are ahead of the pack.
I aim to build a platform like theirs someday (probably not any time soon) but I don't think I'd do any of what they're doing -- it feels unnecessary. Bear with me as I recently learned that they use nomad[0] and some of these suggestions are kubernetes projects but I'd love to hear why the following technologies were decided against (if they were):
- kata-containers[1] (it does the whole container -> VM flow for you, automatically, nemu, firecracker) with multiple VMM options[2]
- linuxkit[3] (let's say you didn't go with kata-containers, this is another container->VM path)
- firecracker-containerd[4] (very minimal keep-your-container-but-run-it-as-a-VM)
- kubevirt[5] (if you just want to actually run VMs, regardless of how you built them)
- Ceph[6] for storage -- make LVM pools and just give them to Ceph, you'll get blocks, distributed filesystems (CephFS), and object gateways (S3/Swift) out of it (in the k8s space Rook manages this)
As an aside to all this, there's also LXD, which supports running "system" (user namespace isolated) containers, VMs (somewhat recent[7][8]), live migration via criu[9], management/migration of underlying filesystems, runs on LVM or zfs[10], it's basically all-in-one, but does fall behind in terms of ecosystem since everyone else is aboard the "cloud native"/"works-with-kubernetes" train.
I've basically how I plan to run a service like fly.io if I ever did -- so maybe my secret is out, but I sure would like to know just how much of this fly.io got built on (if any of it), and/or what was turned down.
[0]: https://news.ycombinator.com/item?id=26745514
[1]: https://github.com/kata-containers/kata-containers
[2]: https://github.com/kata-containers/kata-containers/blob/2fc7...
[3]: https://github.com/linuxkit/linuxkit
[4]: https://github.com/firecracker-microvm/firecracker-container...
[5]: https://github.com/kubevirt/kubevirt
[6]: https://docs.ceph.com/
[7]: https://discuss.linuxcontainers.org/t/running-virtual-machin...
[8]: https://github.com/lxc/lxd/issues/6205
[9]: https://criu.org/Main_Page
[10]: https://linuxcontainers.org/lxd/docs/master/storage
-
Checking Your --privileged Container
Kata Containers https://github.com/kata-containers/kata-containers
What are some alternatives?
hidpi-daemon - Daemon to manage HiDPI and LoDPI monitors on X
firecracker-containerd - firecracker-containerd enables containerd to manage containers as Firecracker microVMs
iced - A cross-platform GUI library for Rust, inspired by Elm
kubevirt - Kubernetes Virtualization API and runtime in order to define and manage virtual machines.
cosmic-text - Pure Rust multi-line text handling
lxd - Powerful system container and virtual machine manager [Moved to: https://github.com/canonical/lxd]
gtk-rs - Rust bindings for GTK 3
sysbox - An open-source, next-generation "runc" that empowers rootless containers to run workloads such as Systemd, Docker, Kubernetes, just like VMs.
libcosmic - WIP library for COSMIC applications
gvisor - Application Kernel for Containers
nvidia-docker - Packaging for https://github.com/NVIDIA/nvidia-docker
ignite - Ignite a Firecracker microVM