Had to Change AI Configuration
This is because of my system, specifically, not because of anything wrong with the AI software.
I saw an article noting the release of a new version of the LLM for the installation I was playing with. I poked a bit, contemplated, and decided I was going to add it to my system.
I ran out of disk space.
That shouldn't happen! There are many generous TB available on that system.
It turns out that Docker had been putting volumes on the little boot partition instead of using the generous space on one of the other partitions. In my servers, I always mount busy or usually large directories, like /home or /opt or /var or /usr/local, to a partition of generous size, if not their own drive/RAID storage. I often have slim storage for the base of the OS, on some systems leveraging the free (fast enough) SSD given away at my local MicroCenter. A 512GB boot SSD with a couple partitions on a few TB HDDs makes the storage easy.
In this case, this is my old desktop, barely promoted to work as a server. I used to have it under my desk and use it 90% of the time for all my needs. As a desktop, almost everything happens on /home, so that was the only folder I'd put on its own hard disk.
The update to the LLM filled the disk and started causing small problems. I stopped the containers, reconfigured them without the volumes, removed the volumes, and recreated the containers using bound folders on a bigger storage drive.
I should step up and rebuild this system right. Almost everything important is on separate drives. I should re-install the OS, as a server instead of desktop, and with an additional drive for a /var partition, at the very least. But, for now, I've got space on my root, and the containers are using the new folders on bigger storage.