<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Danilo Falcão da Silva</title><link>https://falcao.org/tags/containers/</link><description>Recent content in Containers on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 10:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing Snyk with Open Source: SAST, DAST and SCA in 2026</title><link>https://falcao.org/posts/open-source-sast-dast-sca-2026/</link><pubDate>Fri, 22 May 2026 10:00:00 -0300</pubDate><guid>https://falcao.org/posts/open-source-sast-dast-sca-2026/</guid><description>&lt;p>I don&amp;rsquo;t pay for Snyk. Not because it&amp;rsquo;s bad — it&amp;rsquo;s a genuinely good
product — but because there is a free stack that catches the vast
majority of the same issues directly in CI, and the remaining gap
hasn&amp;rsquo;t been worth roughly &lt;strong>$600 per developer per year&lt;/strong> to close.
On a team of fifteen engineers, that&amp;rsquo;s the price of a small EC2
fleet you actually need.&lt;/p>
&lt;p>This post is about the open-source security tooling I actually wire
into pipelines: &lt;strong>Trivy&lt;/strong> for containers, dependencies and IaC,
&lt;strong>Semgrep&lt;/strong> for application code, &lt;strong>Nuclei&lt;/strong> and &lt;strong>OWASP ZAP&lt;/strong> for
the live app, and a few honourable mentions. It&amp;rsquo;s not an exhaustive
catalogue. It&amp;rsquo;s the stack I keep coming back to.&lt;/p></description></item><item><title>Rancher vs Lens: A Platform and a Dashboard, Not the Same Thing</title><link>https://falcao.org/posts/rancher-platform-vs-lens/</link><pubDate>Wed, 20 May 2026 21:15:00 -0300</pubDate><guid>https://falcao.org/posts/rancher-platform-vs-lens/</guid><description>&lt;p>You&amp;rsquo;ll see this comparison on r/kubernetes every couple of months,
phrased as if it&amp;rsquo;s a real choice: &lt;strong>Rancher or Lens?&lt;/strong> The framing is
wrong. They occupy different layers of the stack. Asking which one
&amp;ldquo;wins&amp;rdquo; is like asking whether VS Code beats Kubernetes.&lt;/p>
&lt;p>But the question keeps coming up — usually from someone who has Lens
installed, has heard about Rancher, and is trying to figure out
whether they should swap. So let me lay out what each one actually
is, where they overlap, where they don&amp;rsquo;t, and which one earns a place
in a serious on-prem setup.&lt;/p></description></item><item><title>RKE2 Deserves Some Love: Why It's My On-Prem Kubernetes Pick</title><link>https://falcao.org/posts/rke2-on-prem-kubernetes/</link><pubDate>Tue, 19 May 2026 12:30:00 -0300</pubDate><guid>https://falcao.org/posts/rke2-on-prem-kubernetes/</guid><description>&lt;p>Most of the Kubernetes conversation in 2026 happens around managed
services — &lt;strong>EKS&lt;/strong>, &lt;strong>GKE&lt;/strong>, &lt;strong>AKS&lt;/strong> — and most of the rest happens
around &lt;strong>K3s&lt;/strong> for edge and homelab. Somewhere in the middle, on the
hardware that lives in a rack in a datacenter you can drive to,
there&amp;rsquo;s a Kubernetes story that nobody talks about loudly enough.&lt;/p>
&lt;p>That story is &lt;strong>RKE2&lt;/strong> — the Rancher Kubernetes Engine 2, SUSE&amp;rsquo;s
hardened, security-focused, single-binary distribution designed for
on-premises production. I&amp;rsquo;ve been running it for two years across
two different employers and one home lab, and it&amp;rsquo;s the rare piece of
infrastructure that gets more impressive the longer you live with it.&lt;/p></description></item><item><title>Distrobox, Toolbx, and the 'What Would You Give and What Would You Keep' Question</title><link>https://falcao.org/posts/distrobox-toolbx-podman-docker/</link><pubDate>Tue, 19 May 2026 10:30:00 -0300</pubDate><guid>https://falcao.org/posts/distrobox-toolbx-podman-docker/</guid><description>&lt;blockquote>
&lt;p>&lt;em>&amp;ldquo;What would you give and what would you keep?&amp;rdquo;&lt;/em>
— &lt;strong>Mase&lt;/strong>, &lt;em>From Scratch&lt;/em> (Double Up, 1999)&lt;/p>
&lt;/blockquote>
&lt;p>Mase asked it about rewinding your whole life and starting over. I ask
it every time someone on my team picks a development container stack. Because the
moment you decide to let a container &lt;em>be&lt;/em> your workstation —
not just hold a service, but hold your editor, your shell, your
language toolchains, your AUR packages on top of a Fedora host — you&amp;rsquo;re
making a series of small, ugly trade-offs. &lt;strong>What would you give up
from your bare-metal workflow, and what would you keep?&lt;/strong>&lt;/p></description></item></channel></rss>