<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Volumes on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/volumes/</link><description>Recent content in Volumes on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 25 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/volumes/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><item><title>Chapter 6: Persistent Data with Volumes</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/06-persistent-data-volumes/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/06-persistent-data-volumes/</guid><description>&lt;h2 id="chapter-6-persistent-data-with-volumes"&gt;Chapter 6: Persistent Data with Volumes&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome back, intrepid container explorer! In the previous chapters, you mastered the art of running and managing ephemeral containers. You learned how to launch a simple web server, but what happens to its data when the container stops or is removed? Poof! It&amp;rsquo;s gone. This ephemeral nature is fantastic for stateless applications, but most real-world applications, like databases, logging services, or applications with user-uploaded content, need their data to stick around.&lt;/p&gt;</description></item><item><title>Chapter 6: Docker Storage and Data Persistence</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-6-docker-storage-and-data-persistence/</link><pubDate>Sun, 23 Nov 2025 22:00:12 +0530</pubDate><guid>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-6-docker-storage-and-data-persistence/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the previous chapters, we learned how to create, run, and manage Docker containers. However, one fundamental aspect we haven&amp;rsquo;t deeply explored is how Docker handles data. By default, the data generated by a container is stored within the container&amp;rsquo;s writable layer, which is ephemeral. This means that if you remove the container, all its data is lost. This behavior is problematic for applications that need to store persistent data, such as databases, logs, or user-uploaded files.&lt;/p&gt;</description></item></channel></rss>