toc
ostree
toc | ostree | |
---|---|---|
37 | 41 | |
1,638 | 1,180 | |
0.8% | 1.7% | |
9.0 | 9.5 | |
2 days ago | 2 days ago | |
C | ||
- | GNU General Public License v3.0 or later |
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.
toc
-
Linkerd no longer shipping open source, stable releases
Yup.. CNCF seems to not like this change: https://github.com/cncf/toc/issues/1262
-
Rethinking a Cloud-Native Application Development Paradigm
CNCF Cloud Native Definition v1.0
- CNCF Cloud Native Definition
-
Cilium - CNCF Graduation Public Comment Open
This comes along with a public comment period, you can find the details here, and add your comments, support, remarks at this GitHub PR.
-
Istio moved to CNCF Graduation stage
gRPC had a graduation application open for 3 years. It was rejected very recently: https://github.com/cncf/toc/pull/300.
Reading between the lines, it sounds like the main problem is Google's tight control over the project. Apple contributes to the Swift implementation and MSFT drives the native .NET implementation, but there's little non-Google input in decision-making for Go, Java, C++ core, or any of the implementations that wrap core.
More subjectively, I'm impressed by the CNCF's willingness to stick to their stated graduation criteria. gRPC is widely used (even among other CNCF projects), and comes from the company that organized the CNCF - there must have been a lot of pressure to rubber-stamp the application.
-
Istio has Reached the CNCF Graduated Status
There is some movement: gRPC was recently denied graduation due to perceived problems with its governance.
-
What stops devs from building cloud-native applications?
CNCF Cloud Native Definition v1.0
ostree
-
NixOS Reproducible Builds: minimal ISO successfully independently rebuilt
Ansible makes mutable changes to the OS, task by task.
Nix is immutable. A new change is made entirely new, and only after the build is successful, all packages are "symlinked" to the current system.
Fedora Silverblue is based on ostree [1]. It works similarly like git, but on your root tree. But it requires you to reboot the whole system for the changes to take effect. Since Nix is just symlinked packages, you don't need to reboot the system.
More detailed explanation here [2].
[1]: https://github.com/ostreedev/ostree
[2]: https://dataswamp.org/~solene/2023-07-12-intro-to-immutable-...
- Can't install from flathub
- hello guys everytime i intall a flatpak on fedora this error always happnes how do i fix it
-
PSA: Flatpaks are currently broken on Fedora. Here's a temporary solution.
This one is for the ostree bug currently ongoing: https://github.com/ostreedev/ostree/issues/2900
-
flatpak issue on fedora 38 kde
This sounds related to the ostree bug.
- ostree-system-generator failed with exit status 1 on every boot after update.
-
What do you prefer more and why?
I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.
-
Question about immutability
Other hardening guides mention a Unified Kernel Image as another measure to further improve security. Unfortunately, once more, this is (currently) not supported on Fedora Silverblue. I haven't seen it being done on openSUSE Aeon either. Though, once again, I'd love to be corrected!
-
Does an immutable system really provide enhanced security?
The fedora crew is working on it through ostree though, so both fedora Silverblue and flatpak will be getting it (as well as true immutability) in the future: https://github.com/ostreedev/ostree/issues/2867
-
Silverblue/ Kinoite - real-life shortcomings?
Aside from what has already been mentioned, Unified Kernel Image isn't supported (yet).
What are some alternatives?
foundation - ☁️♮🏛 This repo contains several documents related to the operation of the CNCF. File non-technical issues related to CNCF here.
rpm-ostree - ⚛📦 Hybrid image/package system with atomic upgrades and package layering
envoy - Cloud-native high-performance edge/middle/service proxy
apt2ostree - Build ostree images based on Debian/Ubuntu
fedora-coreos-tracker - Issue tracker for Fedora CoreOS
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
Flatcar - Flatcar project repository for issue tracking, project documentation, etc.
flatpak - Linux application sandboxing and distribution framework
RealCloudLabs - Labs designed to help students learn cloud skills
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
istio - Connect, secure, control, and observe services.
mkosi - 💽 Build Bespoke OS Images