I’m in the process of planning upgrades for my server, and I’m trying to figure out the “best” drive configuration for Docker. My general understanding would be that the containers should be running from an SSD, and any storage (images, videos, documents) should use a volume on an HDD.
Is it as simple as changing the data-root to point to the SSD, and keep my external volumes on the HDD as defined in my existing compose files? I’ve already moved data-root once b/c the OverlayFS was chewing up the limited space on the OS drive, so that process isn’t daunting.
If there’s a better way to configure Docker, I’m open to it, as long as it doesn’t require rebuilding everything from scratch.
For reference, the server is running Debian Bookworm on an older i5 3400 with 32GB RAM.
You must log in or register to comment.
Unless I’m misunderstanding, I do believe it is that simple, yes.
I think you’re right. I’m just trapped in the cycle of over-thinking and second guessing my knowledge and capabilities.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters NUC Next Unit of Computing brand of Intel small computers SSD Solid State Drive mass storage ZFS Solaris/Linux filesystem focusing on data integrity
3 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #819 for this sub, first seen 20th Jun 2024, 21:45] [FAQ] [Full list] [Contact] [Source code]
If there’s a better way to configure Docker, I’m open to it, as long as it doesn’t require rebuilding everything from scratch.
You could try using lvmcache (block device level) or bcachefs (filesystem level caching) or something like that, have rotational storage be the primary form of storage but let the system use SSD as a cache. Dunno what kind of performance improvements you might expect, though.
