My production Postgres container kept running on an orphaned Portainer volume after an upgrade, and nothing warned me
Upgrading a container like Portainer is normally one of the least stressful parts of running a homelab. I have done it many times without a second thought. The last upgrade I did also felt normal because everything was working exactly the way it was supposed to. Weeks later, I was pulling compose files from my homelab for an article I was working on. But the compose files weren’t where I expected them to be. Those missing files made me investigate, and what I found underneath was a mess.
Upgrading a container like Portainer is normally one of the least stressful parts of running a homelab. I have done it many times without a second thought. The last upgrade I did also felt normal because everything was working exactly the way it was supposed to. Weeks later, I was pulling compose files from my homelab for an article I was working on. But the compose files weren’t where I expected them to be. Those missing files made me investigate, and what I found underneath was a mess.
Phillip Moosmann
Germany
Germany
Published by: aplhsindia.in
