<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Commentary of Takao</title><link>https://takao.blog/ko/tags/containers/</link><description>Recent content in Containers on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>ko</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sun, 12 Jul 2026 04:12:51 +0900</lastBuildDate><atom:link href="https://takao.blog/ko/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Reducing Docker Image Sizes with Multi-Stage Builds</title><link>https://takao.blog/ko/web/docker-multi-stage-build-reduction/</link><pubDate>Thu, 20 Mar 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/ko/web/docker-multi-stage-build-reduction/</guid><description>&lt;img src="https://takao.blog/img/thumbnail/docker-multi-stage-build-reduction-ko.png" alt="Featured image of post Reducing Docker Image Sizes with Multi-Stage Builds" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;Keeping Docker image footprints small is critical for accelerating 배포 cycles, lowering storage costs, and tightening security by shrinking the container&amp;rsquo;s attack surface.&lt;/p&gt;
&lt;p&gt;However, a naive Dockerfile construction often bundles compile-time dependencies (like gcc, headers, build caches) and testing tools directly into the final runtime image. This inflates the image size from a few megabytes to hundreds or gigabytes.&lt;/p&gt;
&lt;p&gt;To solve this, Docker introduced &lt;strong&gt;Multi-Stage Builds&lt;/strong&gt;. This article reviews the core practices of multi-stage architectures, demonstrating image footprint 최적화 using a TypeScript Node.js project.&lt;/p&gt;</description></item><item><title>Proxmox LXC Containers: Complete Management Guide</title><link>https://takao.blog/ko/web/proxmox-lxc-containers/</link><pubDate>Wed, 22 May 2024 00:00:00 +0000</pubDate><guid>https://takao.blog/ko/web/proxmox-lxc-containers/</guid><description>&lt;img src="https://takao.blog/img/thumbnail/proxmox-lxc-containers-ko.png" alt="Featured image of post Proxmox LXC Containers: Complete Management Guide" /&gt;&lt;h2 id="what-is-lxc"&gt;What is LXC?
&lt;/h2&gt;&lt;p&gt;LXC (Linux Containers) is an OS-level virtualization method that runs multiple isolated Linux systems on a single host using a shared kernel. Unlike full virtual machines, LXC containers share the host OS kernel while maintaining their own filesystem, processes, and 네트워크 stack. This design makes them extremely lightweight and fast to start.&lt;/p&gt;
&lt;h2 id="lxc-vs-virtual-machines"&gt;LXC vs Virtual Machines
&lt;/h2&gt;&lt;p&gt;The choice between LXC containers and VMs depends on your isolation and 성능 requirements:&lt;/p&gt;</description></item></channel></rss>