<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containerized Applications on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/containerized-applications/</link><description>Recent content in Containerized Applications on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/containerized-applications/index.xml" rel="self" type="application/rss+xml"/><item><title>Data That Stays - Introduction to Docker Volumes</title><link>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-05-docker-volumes/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-05-docker-volumes/</guid><description>&lt;h2 id="data-that-stays---introduction-to-docker-volumes"&gt;Data That Stays - Introduction to Docker Volumes&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring Docker master! So far, we&amp;rsquo;ve learned how to create, run, and manage containers. You&amp;rsquo;ve seen how powerful they are for packaging applications. But there&amp;rsquo;s a tiny &amp;ldquo;gotcha&amp;rdquo; we need to address: what happens to your data when a container stops or gets removed? Poof! It&amp;rsquo;s gone. That&amp;rsquo;s not ideal for most real-world applications, right?&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to tackle this challenge head-on by introducing &lt;strong&gt;Docker Volumes&lt;/strong&gt;. You&amp;rsquo;ll discover how to make your containerized applications store data persistently, ensuring your important information survives even if your containers don&amp;rsquo;t. This is a fundamental concept for building robust, production-ready Docker applications, so get ready to make your data truly &lt;em&gt;stay&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>