I’ll start this with that happens quite a bit on Windows as well, but I’ve had an amazing streak the past two months with Docker instances being unusable right after a new image with every update requiring more digging to find out why it broke.
This is usually followed up by an AI telling me that it’s a known issue in the forums and to roll back to a specific version until a fix is issued. I’m the target for the bugs.
As a note this is not the anti-linux anti-docker rant you think it is and the only point is to back up so you can roll back if you need to. See it’s possible to point to an error and say “guys, this is at fault, but let’s talk about what to do so you don’t get impacted.”
Now my assumption here is this is not the norm and that I’ve simply started at a time that the apps I’ve chosen are in a tizzy. That or the updater is not functioning properly and I’m just being gaslit by AI with links that support its assumptions. I’ve been using Docker a lot since getting that Orico Metabox.
Updating Home Assistant killed HACS. Installing HACS again was required. OK, not Home Assistant’s fault, but the dependencies were killed. Droplet and one other integration also died and had to be set up again. Meh, no big deal.
Updating LM Studio killed my OpenClaw integration. Much googling has resulted in a list of changes I need to make to get them to work together again. I don’t need OpenClaw, but it’s something I was playing with (and no, it doesn’t have access to anything and I know the risks and am not taking them.)
Updating Openclaw – well, probably did nothing but it’s no longer working with my LM Studio even after latest upgrade.
Updating qbittorrent – it just stopped working. Nothing was displayed in console (it just stopped without any message and waited). Turned out it had a lock file set and I just stumbled across it. I suspect a graceless shutdown when the Docker updater started pushing the update.
Updating Uptime-Kuma – that worked, but the updating process hung downloading the bits of it. Guessing an intermittent network issue on that. Just sat for what seemed like forever before failing. Restarting the update fixed that.
Updating Glueten VPN gateway broke interface with qbittorrent and now it won’t set ports due to a TLS error.
Plex, well that has upgraded flawlessly. Thank you Plex.
I suspect I’m going to fall into the habits of 1) snapshotting the system, 2) update, 3) evaluate and possibly roll back.
Maybe I just came in at the harmonic convergence of minor issues in some very specialized software.
