<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nodejs on Lorbic</title><link>http://localhost:1313/tags/nodejs/</link><description>Recent content in Nodejs on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Feb 2026 13:45:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/nodejs/index.xml" rel="self" type="application/rss+xml"/><item><title>Fast Docker CI: Stop Rebuilding Container Images on Every Commit</title><link>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</link><pubDate>Sun, 15 Feb 2026 02:30:00 +0530</pubDate><guid>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</guid><description>&lt;p>I used to rebuild my Docker image every time I fixed a typo. A one-line change meant waiting 2-3 minutes for Docker to rebuild layers, reinstall dependencies, and restart the container. I thought this was just the cost of containerized development.&lt;/p>
&lt;p>Then I discovered runtime containers. Same isolated environment, same reproducibility, but code changes reflect instantly. No rebuilds. No waiting. The runtime lives in the container, the code lives on the host.&lt;/p></description></item></channel></rss>