<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cgroups on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/cgroups/</link><description>Recent content in Cgroups on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Tue, 01 Nov 2016 15:09:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/cgroups/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux containers in 500 lines of code</title><link>http://karpoke.ignaciocano.com/2016/11/01/linux-containers-in-500-lines-of-code/</link><pubDate>Tue, 01 Nov 2016 15:09:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/11/01/linux-containers-in-500-lines-of-code/</guid><description>&lt;p&gt;Relatd:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I’ve used Linux containers directly and indirectly for years, but I wanted
to become more familiar with them. So I wrote some code. This used to be 500
lines of code, I swear, but I’ve revised it some since publishing; I’ve
ended up with about 70 lines more.&lt;/p&gt;
&lt;p&gt;I wanted specifically to find a minimal set of restrictions to run untrusted
code. This isn’t how you should approach containers on anything with any
exposure: you should restrict everything you can. But I think it’s important
to know which permissions are categorically unsafe!&lt;/p&gt;</description></item></channel></rss>