<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Proxmox on BitPage</title><link>https://bitpage.me/tags/proxmox/</link><description>Recent content in Proxmox on BitPage</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Jul 2026 11:35:00 +0000</lastBuildDate><atom:link href="https://bitpage.me/tags/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>How to migrate a stateful Docker app off a server with a dying disk</title><link>https://bitpage.me/infra/migrate-docker-app-dying-disk/</link><pubDate>Fri, 24 Jul 2026 11:35:00 +0000</pubDate><guid>https://bitpage.me/infra/migrate-docker-app-dying-disk/</guid><description>Short answer: When the source server&amp;rsquo;s disk fails on writes but still reads fine, treat it as read-only hardware. Stream pg_dump -Fc over SSH straight to the target machine, pull Docker images from your registry instead of rebuilding end-of-life Dockerfiles, and anchor every rsync exclude with a leading slash. That moved a 14-service app with a 12 GB PostgreSQL database onto a new node without a single write to the failing disk.</description></item></channel></rss>