<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Lorbic</title><link>http://localhost:1313/tags/docker/</link><description>Recent content in Docker on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/docker/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><item><title>Docker Volume Backup: The 1-Line Command You Should Be Using (Instead of tar)</title><link>http://localhost:1313/how-to-backup-and-restore-docker-volumes/</link><pubDate>Sun, 13 Apr 2025 07:14:00 +0000</pubDate><guid>http://localhost:1313/how-to-backup-and-restore-docker-volumes/</guid><description>&lt;h1 id="how-to-backup-and-restore-docker-volumes-between-machines">How to Backup and Restore Docker Volumes Between Machines&lt;a class="anchorjs-link" href="#how-to-backup-and-restore-docker-volumes-between-machines" aria-label="Link to section: How to Backup and Restore Docker Volumes Between Machines">&lt;/a>&lt;/h1>&lt;p>When working with Docker, persistent data is often stored in volumes. Unlike container filesystems, volumes survive restarts and recreations. But what if you need to move this data from one machine to another?&lt;br>
Here&amp;rsquo;s a quick and reliable way to back up a Docker volume on one computer and restore it on another.&lt;/p></description></item><item><title>How to Install Docker Desktop on Another Drive in Windows</title><link>http://localhost:1313/docker-custom-installation-location-windows/</link><pubDate>Sat, 27 Jan 2024 13:11:47 +0000</pubDate><guid>http://localhost:1313/docker-custom-installation-location-windows/</guid><description>&lt;p>Docker Desktop on Windows installs to your C: drive by default. When you pull large images (often 1.5GB each), add build layers, and stack containers, the ext4.vhdx file that holds all your container data bloats fast. This guide shows you how to route Docker to a secondary drive entirely, using CLI flags instead of the GUI.&lt;/p>
&lt;h2 id="quick-start">Quick Start&lt;a class="anchorjs-link" href="#quick-start" aria-label="Link to section: Quick Start">&lt;/a>&lt;/h2>&lt;p>Uninstall any existing Docker first. Then open PowerShell as admin and navigate to your Downloads folder where the installer is. Run:&lt;/p></description></item></channel></rss>