<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>devcontainer on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/devcontainer/</link>
    <description>Recent content in devcontainer on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Jul 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/devcontainer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Serving LLMs with Dev Containers: A New Rabbit Hole</title>
      <link>https://jackliusr.github.io/posts/2026/07/serving-llms-with-dev-containers-a-new-rabbit-hole/</link>
      <pubDate>Sun, 26 Jul 2026 20:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/07/serving-llms-with-dev-containers-a-new-rabbit-hole/</guid>
      <description>Serving LLMs with Dev Containers: A New Rabbit Hole One of the interesting things about working with AI is that you often discover new ideas when you’re exploring something completely different.
 I never imagined I would write about serving Large Language Models (LLMs) using Dev Containers. Although I’ve been using the vLLM container for quite some time, I always thought of it simply as another containerized application running in Kubernetes or Docker.</description>
    </item>
    
  </channel>
</rss>
