<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Container on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/multi-container/</link><description>Recent content in Multi-Container 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/multi-container/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 7: Composing Multi-Container Applications</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/07-compose-applications/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/07-compose-applications/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 7! So far, you&amp;rsquo;ve mastered the art of running individual Linux containers on your Mac using Apple&amp;rsquo;s powerful &lt;code&gt;container&lt;/code&gt; CLI. You&amp;rsquo;ve built images, run single services, and even understood the fundamental architecture that makes it all possible. That&amp;rsquo;s fantastic!&lt;/p&gt;
&lt;p&gt;But what happens when your application isn&amp;rsquo;t just one simple service? Most modern applications are a collection of interconnected services: a web front-end, a backend API, a database, a caching layer, and perhaps more. Managing each of these as separate &lt;code&gt;container run&lt;/code&gt; commands can quickly become a tangled mess. This is where the concept of &amp;ldquo;composing&amp;rdquo; multi-container applications comes into play.&lt;/p&gt;</description></item><item><title>Chapter 7: Docker Compose - Orchestrating Multi-Container Applications</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/docker-compose-multi-container/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/docker-compose-multi-container/</guid><description>&lt;h2 id="introduction-to-orchestrating-multi-container-applications"&gt;Introduction to Orchestrating Multi-Container Applications&lt;/h2&gt;
&lt;p&gt;Welcome back, future DevOps maestro! In our last chapter, we mastered the art of running single Docker containers and even crafted our own custom images using &lt;code&gt;Dockerfile&lt;/code&gt;. That was a fantastic start, but in the real world, applications are rarely just one isolated container. Think about a typical web application: you&amp;rsquo;ll likely have a web server, a backend API, a database, maybe a cache, and more – all needing to talk to each other.&lt;/p&gt;</description></item><item><title>Chapter 7: Multi-Container Applications with Docker Compose</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-7-multi-container-applications-with-docker-compose/</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-7-multi-container-applications-with-docker-compose/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In previous chapters, we learned how to build and run individual Docker containers. While this is powerful for isolated services, real-world applications often consist of multiple interconnected services—a web server, a database, a cache, a message queue, etc. Managing these services individually with &lt;code&gt;docker run&lt;/code&gt; can quickly become cumbersome and error-prone. This is where Docker Compose comes into play.&lt;/p&gt;
&lt;p&gt;Docker Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application&amp;rsquo;s services, networks, and volumes. Then, with a single command, you can create and start all the services from your configuration. This chapter will delve into the core concepts of Docker Compose, its benefits, and how to use it effectively to orchestrate complex applications.&lt;/p&gt;</description></item><item><title>Chapter 9: Advanced Docker Concepts</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-9-advanced-docker-concepts/</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-9-advanced-docker-concepts/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 9 of our guide on Docker Engine 29.0.2! Having covered the fundamentals of Docker, including building images, running containers, and basic networking, we are now ready to dive into more advanced concepts. This chapter will equip you with the knowledge to manage complex, multi-container applications, orchestrate services across multiple hosts, and optimize your Docker workflows for production environments. We&amp;rsquo;ll explore Docker Compose for multi-service applications, Docker Swarm for native orchestration, advanced networking and volume strategies, and efficient image building techniques like multi-stage builds.&lt;/p&gt;</description></item></channel></rss>