<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/bind-mounts/</link><description>Recent content in Bind Mounts 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/bind-mounts/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 10: Integrating with Development Workflows and IDEs</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/10-dev-workflow-integration/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/10-dev-workflow-integration/</guid><description>&lt;h2 id="chapter-10-integrating-with-development-workflows-and-ides"&gt;Chapter 10: Integrating with Development Workflows and IDEs&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow developer! In previous chapters, you&amp;rsquo;ve mastered the fundamentals of creating and running Linux containers on your Mac using Apple&amp;rsquo;s powerful new &lt;code&gt;container&lt;/code&gt; CLI. You&amp;rsquo;ve built images, understood the underlying architecture, and even tackled some advanced networking. But what about your daily grind? How do these amazing tools fit into your existing development workflow?&lt;/p&gt;
&lt;p&gt;This chapter is all about bridging that gap. We&amp;rsquo;ll explore how to seamlessly integrate Apple&amp;rsquo;s &lt;code&gt;container&lt;/code&gt; tool with your favorite Integrated Development Environments (IDEs) like VS Code, making your containerized development experience on macOS as smooth and efficient as possible. We&amp;rsquo;ll dive into practical patterns like bind mounts for live code changes, managing environment variables, and even debugging applications running inside your containers directly from your host machine. Get ready to supercharge your development!&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>