<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Container on Aadi</title>
		<link>https://aadi-blogs.web.app/tags/container/</link>
		<description>Recent content in Container on Aadi</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 11 Sep 2026 18:00:42 -0400</lastBuildDate>
		
			<atom:link href="https://aadi-blogs.web.app/tags/container/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Spinning up a simple k3s to manage a local LLM Docker Container</title>
				<link>https://aadi-blogs.web.app/blog/intro-to-k3s/</link>
				<pubDate>Fri, 11 Sep 2026 18:00:42 -0400</pubDate>
				<guid>https://aadi-blogs.web.app/blog/intro-to-k3s/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://github.com/codecalligrapher/llm-serving-vllm-k8s&#34;&gt;Link to Github&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;In this blog post, I walk through how to take a lone Docker image and use &lt;code&gt;k3s&lt;/code&gt; to manage it on a single-node machine (i.e. my desktop). The idea behind Docker is an isolated, self-sufficient container that can run anywhere, &lt;code&gt;k3s&lt;/code&gt; and its bigger brother &lt;code&gt;k8s&lt;/code&gt; (Kubernetes) is used to manage, in a declarative fashinon, these containers.&lt;/p&gt;&#xA;&lt;p&gt;The core model of Kubernetes, and the main difference from simply calling &lt;code&gt;docker run&lt;/code&gt; is the &lt;em&gt;declarative reconciliation&lt;/em&gt;. Kubernetes is a control system built around a single loop:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
