<?xml 
version="1.0" encoding="utf-8"?>
<rss version="2.0" 
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
>

<channel xml:lang="fr">

	<title>Demystifying container runtimes [LWN.net] - commentaires</title>
	<link>http://clx.asso.fr/spip/?Demystifying-container-runtimes-LWN-net</link>
	<description>
Demystifying container runtimes [LWN.net] &#9659;https://lwn.net/Articles/741897 A container is created from a container image. Images are tarballs with a JSON configuration file attached. Images are often nested : for example this Libresonic image is built on top of a Tomcat image that depends (eventually) on a base Debian image. This allows for content deduplication because that Debian image (or any intermediate step) may be the basis for other containers. A container image is typically (&#8230;)
</description>
	<language>fr</language>
    <generator>SPIP - www.spip.net</generator>

	<image>
		<title>Demystifying container runtimes [LWN.net]</title>
		<url>http://clx.asso.fr/spip/local/cache-vignettes/L144xH132/arton4432-fdb5a.png?1764630590</url>
		<link>http://clx.asso.fr/spip/?Demystifying-container-runtimes-LWN-net</link>
		<height>132</height>
		<width>144</width>
	</image>






</channel>

</rss>
