<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tmpfs on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/tmpfs/</link><description>Recent content in Tmpfs on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 23 Nov 2025 22:00:12 +0530</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/tmpfs/index.xml" rel="self" type="application/rss+xml"/><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>