<?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>volumes on Dileep Kumar</title>
    <link>https://dileepkumar.dev/tags/volumes/</link>
    <description>Recent content in volumes on Dileep Kumar</description>
    <image>
      <title>Dileep Kumar</title>
      <url>https://dileepkumar.dev/papermod-cover.png</url>
      <link>https://dileepkumar.dev/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 14 Jan 2025 00:01:00 +0530</lastBuildDate><atom:link href="https://dileepkumar.dev/tags/volumes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Volumes and Bind Mounts - A Comprehensive Guide to Persisting Data</title>
      <link>https://dileepkumar.dev/post/docker-volumes-and-bind-mounts/</link>
      <pubDate>Tue, 14 Jan 2025 00:01:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/docker-volumes-and-bind-mounts/</guid>
      <description>Introduction A core principle of Docker is that containers should be ephemeral and stateless. This means that any data created inside a container&amp;rsquo;s writable layer is lost forever when the container is removed. While this is great for creating predictable and clean environments, it poses a significant challenge for any application that needs to save data—like databases, user uploads, or logs.
To solve this, Docker provides three primary mechanisms for getting data into and out of containers: Volumes, Bind Mounts, and tmpfs mounts.</description>
    </item>
    
  </channel>
</rss>
