There is a virtuous cycle in the technology that pushes the boundaries of what is being built and how it is used. New technology develops and attracts the attention of the world. People begin to experiment and identify new applications, use cases and approaches to maximize the potential of innovation. These cases use considerable value by fueled the demand for the subsequent iteration of innovation, and, in turn, the new wave of innovators creates cases of using the next generation, causing further achievements.
The containers became the basis of modern, cloud development software that supports new cases of use and approaches to creating sustainable, scale and portable applications. It also contains the keys to the following software delivery innovations while at the same time requiring the evolution for design safety, constantly updated software and serves as a means to get there.
Below I talk through some of the innovations that led to our container revolution, as well as some of the new software development features that led to this splatter, which thoroughly based the world to move away from traditional Linux distributions and to the new approach to open source software.
Iterations approached us to ubiquity
There were many innovations that paved the way for a safer, performance with open source. In the interests of your time and counting my word I urge three specific milestones. Each step, from the Linux containers (LXC) to Docker and ultimately the Open Container (OCI) initiative, built on its predecessor, resolving restrictions and unlocking new opportunities.
LXC laid the foundation using the capabilities of Linux kernel (namely croups and name spaces) to create a light, isolated environment. For the first time, developers could pack applications with their dependencies, offering a certain sequence in different systems. However, the complexity of LXC for users and the lack of a standardized image distribution catalog was hindered by extensive acceptance.
Docker appeared as a change in games, democratization of container technology. This simplified the process of creating, launching and sharing containers, making them available to a wider audience. The Docker user interface and the creation of Docker Hub, the central storage for container images, contributed to the live ecosystem. This simplicity in using the rapid acceptance, but also caused concern about blocking suppliers and the need for interaction.
Recognizing the potential for fragmentation, OCI (Open Containers initiative) entered into standardization of container and time formats. Determining open technical characteristics, OCI guaranteed that containers can be built and operated on different platforms, contributing to a healthy, competitive landscape. Projects such as Runc and Containerd were born with OCI, created a general basis for containers and included great tolerance and interaction.
OCI standards also allowed Kubernetes (another neutral supplier standard) to become a truly portable platform capable of working on a wide range of infrastructure and allow organizations to consistently organize their applications in various cloud suppliers and local environments. This standardization and related innovations unlock all the potential of containers, opening the way to their ubiquitous presence in modern software development.
(Container) software eats the world
Progress in Linux, rapid democratization of containers through Docker and standardization of OCI were due to the need, with the evolution of cloud applications the use of the orchestration and standardization. These characteristics concerning the cloud-rod application also emphasize why the overall purpose to Linux Distros no longer serves software developers with the safest, updated bases that need to be developed on:
MicroService architecture: Cloud-Native Applications is usually built as a collection of small independent services, and each microservice performs a specific function. Each of these microservice can be built, deployed and maintained independently, which provides a huge amount of flexibility and stability. Because each microservice is independent, software builders do not require comprehensive software packages to launch a microservice, relying only on naked essentials in the container.
Resources that are aware of resources and effective: apps concerning a cloud built for effective and resource to minimize the load on infrastructure. This removed approach, of course, coincides well with the containers and the ephemeral deployment strategy, with new containers are constantly unfolding and other loads are updated to the last available code. This reduces the risk of safety by using the latest software packages, rather than waiting for Distro Patches and Backports.
Portability: Additions to the cloud are designed so that they are portable, with consistent performance and reliability, regardless of where the application is running. As a result of the containers, the standardization of the environment, the developers can go beyond the age -old “, it worked perfectly by my car” headaches of the past.
The virtuous cycle of innovation that manages new cases of use and ultimately new innovations is clear when it comes to container and wide adoption of cloud applications. Critically, this point of dissolution of innovation and requirements of use caused the incredible speed change in open source software-we reached the point when the safety, productivity and shortcomings of traditional “frozen time” Linux Distros exceeds the acquaintance and perception of the latest generation of the software delivery.
So, what should the open source software shipping look like?
Enter: Chainguard OS
In order to meet modern safety, performance and performance expectations, software builders need the latest software designed for their use, without any CVES that leads to a risk to business (and a “fix” security list). Creating good on these parameters requires more than just making the past. Instead, the next generation of open source software delivery should start from the safe, updated software: up.
Therefore Couple Built this new dystrophic approach, constantly rebuilding software packages not on distribution down, but on top sources that remove vulnerabilities and add improvements to performance. We call it Cartogenic OS.
Chaingleard OS serves as the basis for extensive safety, efficiency and performance results today provided by Chificeard products, “overcoming” a fast -growing catalog from more than 1000 container images.
Chainguard OS follows four key principles to make this possible:
- Permanent Integration and Delivery: emphasizes continuous integration, testing and release of software packages at the top course, providing an orderly and effective development pipeline through automation.
- Nano updating and restructuring: contributes to additional updates and recovers compared to the main release upgrades, providing smoother transitions and minimizing devastating changes.
- Minimum, hardened, unchanged artifacts: deprives the unnecessary upheaval of the provider from the software artifacts, which makes the parties packages and additional for the user at the same time increasing the safety by solidifying measures.
- Minimization of Delta: The deviations from the ascending to the minimum, having included additional patches only if necessary and only until a new release is cut.
Apparently, the best way to emphasize the value of Chaingleard OS is to see the impact on Chaigord’s images.
On the screenshot below (and viewed there), you can see the comparison between the external
In addition to the very clear divergence in the count of vulnerability, the size difference between the two drawings of the container should be studied. The Chaingleard image consists of only 6% of the alternative image with open source.
Along with the minimized image size, the Chainguard image was the last updated just an hour before Screengrab, what happens daily:
The rapid scan of data on origin and SBOM illustrates the integrity at the end and the invariance of the artifacts-a peculiar full label of nutrition, which emphasizes safety and transparency, which can provide a modern approach to open source software.
Each Chainleard image acts as a practical example of Chaingleard OS value by offering a sharp alternative to what happened earlier. Apparently, the highest indicator is the feedback we received from customers who shared the way the Chainer container helped eliminate CVE, provide their supply chains, achieve and maintain matching, and reduce the developer’s work, which allows them to restore the resources of valuable developers.
Our conviction is that the principles and approach of Chaingleard OS can apply to different use cases, expanding the benefits of constant resumption of the software package from the source to be even more open source.
If you considered it useful, be sure to check out Our document on this topic either Contact our team Talk to a specialist in the distribution approach of Chaigord.
Note: This article is written and contributed Dastin Kirkland – VP engineering in Couple.
