<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bind-Mounts on Dev &amp; Platform Engineering Hub</title><link>https://rhidayat.work/topics/bind-mounts/</link><description>Recent content in Bind-Mounts on Dev &amp; Platform Engineering Hub</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Rachmat Hidayat</copyright><lastBuildDate>Sun, 09 Aug 2026 16:35:00 +0000</lastBuildDate><atom:link href="https://rhidayat.work/topics/bind-mounts/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Ep 4: Volumes &amp; Data Persistence</title><link>https://rhidayat.work/series/docker/04-docker-volumes-and-data-persistence/</link><pubDate>Sun, 09 Aug 2026 16:35:00 +0000</pubDate><guid>https://rhidayat.work/series/docker/04-docker-volumes-and-data-persistence/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 By default, all files created inside a container are stored on a writable container layer. When that container is deleted, the data is destroyed. Docker Volumes solve this by storing data outside the container filesystem.
&lt;/div&gt;</description></item></channel></rss>