<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux-Foundation on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/linux-foundation/</link><description>Recent content in Linux-Foundation on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/linux-foundation/index.xml" rel="self" type="application/rss+xml"/><item><title>OCI (Open Container Initiative)</title><link>https://lesitedefrancois.be/en/security/oci/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/oci/</guid><description>&lt;p&gt;&lt;strong&gt;The Open Container Initiative (OCI)&lt;/strong&gt; is a Linux Foundation project founded in June 2015 by Docker, CoreOS, and others to prevent the container ecosystem from fragmenting around proprietary formats. It maintains three interlocking specifications that together describe the complete lifecycle of a container: how an image is structured, how it is transported, and how it is run. Any tool that conforms to these specs — builder, registry, runtime — is interoperable with any other conformant tool, which is why an image built by &lt;code&gt;buildah&lt;/code&gt; can be pushed to a registry running Harbor, pulled by containerd, and executed by a runtime written in Rust.&lt;/p&gt;</description></item></channel></rss>