Best NVMe SSDs for Docker Builds: TBW, Capacity, and Cooling

The best NVMe SSDs for Docker builds are not necessarily the drives with the largest sequential-read number on the box. Container work creates a mix of layer extraction, package-cache writes, metadata updates, and repeated reads across many small files. Capacity, endurance, cooling, and a sane cache strategy matter alongside peak speed.

I compared the current Docker storage documentation with manufacturer specifications for three widely available PCIe 4.0 drives. The goal is not to manufacture a benchmark I cannot reproduce on your workstation. It is to show which specifications affect a development workload, which numbers are mostly marketing, and what to measure before spending money.

Why Docker Builds Put Pressure on Storage

Docker images are assembled from layers. On current fresh installations, Docker Engine 29 uses the containerd image store by default; upgraded installations may still use the classic overlay2 driver. Docker’s documentation notes that the containerd store keeps both compressed and uncompressed image data, so it can use more disk capacity than the older storage path.

With overlay2, the first write to a file from a lower image layer can trigger a full-file copy_up into the writable layer. A build also creates and reads package caches, source trees, temporary objects, and image layers. That workload is not represented by a single sequential-read score.

Before blaming the SSD, check the build itself. Docker recommends ordering layers to protect cache hits, keeping the build context small, and using cache mounts for package managers. A faster drive cannot recover time lost because every source change invalidates a dependency-install layer. See Docker’s official build-cache guidance before buying hardware.

Start with Capacity, Not the Peak MB/s Number

Run docker system df and docker buildx du to see how much space images, containers, volumes, and build cache currently consume. Then add the working tree, local databases, virtual machines, and enough free space for firmware garbage collection to work effectively.

docker system df
docker buildx du
docker info --format '{{json .DriverStatus}}'

A 1TB drive can be sufficient for one active codebase. A developer keeping several multi-platform builders, Android toolchains, local model files, and database snapshots may run out of room quickly. Capacity pressure causes manual pruning and makes it tempting to mix irreplaceable source data with disposable caches.

Docker stores daemon data under /var/lib/docker by default on Linux. The containerd image store uses a separate path for image contents and snapshots, so changing Docker’s data-root does not automatically move that containerd data. Confirm the active backend before designing a dedicated build drive.

TBW Is More Useful Than a Hero Benchmark

TBW, or terabytes written, is the manufacturer’s endurance limit used with the warranty period. It is not a prediction that the drive will fail one byte later. It does give you a consistent way to compare capacities within a product family.

The official specifications rate the 2TB Samsung 990 PRO and 2TB WD_BLACK SN850X at 1,200 TBW. The SN850X data sheet states that its TBW calculation uses the JEDEC client workload and that warranty coverage ends at five years or the endurance limit, whichever comes first. Crucial also lists 1,200 TBW for the 2TB T500.

Those values are far more informative for a write-heavy development machine than comparing 7,300 MB/s with 7,450 MB/s. Your motherboard generation, thermal limit, filesystem, build graph, and cache-hit rate can dominate that small peak-speed difference.

Three PCIe 4.0 Choices Worth Comparing

Samsung 990 PRO: high-end desktop choice

Samsung lists the 2TB 990 PRO with heatsink at up to 7,450 MB/s sequential read and 6,900 MB/s sequential write. A factory-heatsink version is available, which is useful when the motherboard lacks an M.2 cover or the slot sits near a hot GPU.

Check the current Samsung 990 PRO 2TB listings on Amazon. Match the exact capacity, heatsink option, and model number rather than trusting a search-result thumbnail.

WD_BLACK SN850X: TLC and clear endurance specs

SanDisk’s July 2025 data sheet identifies the SN850X as TLC 3D NAND. The 2TB model is rated for up to 7,300 MB/s sequential read, 6,600 MB/s sequential write, 1,200 TBW, and a five-year limited warranty. Both bare and factory-heatsink versions are listed.

Check the current WD_BLACK SN850X 2TB listings on Amazon. The heatsink model is taller, so verify clearance in compact systems and laptops.

Crucial T500: another 2TB, 1,200-TBW option

Crucial offers the 2TB T500 in versions with and without a heatsink and lists a five-year limited warranty with 1,200 TBW endurance. It belongs on the same shortlist when pricing changes, but compare the exact SKU because heatsink and non-heatsink models are easy to confuse.

Check the current Crucial T500 2TB listings on Amazon. Do not pay extra for a bundled heatsink if your motherboard already has a suitable M.2 thermal plate.

Full disclosure: the three Amazon links above are affiliate links. I may earn a commission from qualifying purchases at no extra cost to you.

Cooling Matters During Repeated Builds

Peak specifications are measured under controlled conditions. A controller that reaches its thermal limit during repeated image builds can reduce speed until it cools. Desktop boards often include an M.2 plate; small-form-factor systems may have poor airflow; laptops may not accept a heatsink at all.

Read the motherboard or laptop service manual before ordering. Confirm M.2 2280 support, PCIe generation, available lanes, single- or double-sided clearance, and whether removing a factory heatsink affects the drive warranty. Do not stack a motherboard plate on top of a factory heatsink.

On Linux, the open-source nvme-cli tool can read the drive’s SMART and health information. Record temperature and data-unit writes during your normal workload rather than treating one synthetic test as the answer:

sudo nvme list
sudo nvme smart-log /dev/nvme0

Replace the device name with the one reported on your machine. These commands inspect the drive; they do not prove that storage is the build bottleneck.

Measure Cold and Warm Builds Separately

A useful comparison records at least two cases. A cold build exercises downloads, extraction, compilation, and writes. A warm build shows whether the Dockerfile and cache layout are working. Record the same commit, builder, network conditions, and command each time.

/usr/bin/time -v docker buildx build --load -t storage-test:latest .
docker system df
docker buildx du

Do not clear caches on a production machine merely to create a prettier chart. If a cold-cache test is necessary, use an isolated builder or disposable test host. Also watch CPU utilization and network transfer: an idle SSD during a slow build points elsewhere.

My Buying Rule for a Docker Workstation

I would choose capacity first, then endurance, physical compatibility, warranty, and cooling. After those pass, I would compare price. For most PCIe 4.0 development systems, the practical difference between these three drives is more likely to come from capacity headroom and thermal behavior than a small gap in advertised sequential speed.

If the drive will also hold irreplaceable data, remember that endurance is not a backup. Keep source in version control and maintain a separate backup. My TrueNAS drive guide covers storage roles where redundancy and recovery matter more than workstation build speed, while the homelab hardware guide covers the rest of a self-hosted system.

Start by measuring cache size and checking your M.2 slot. Then compare the exact capacity and warranty terms instead of buying whichever listing has the biggest MB/s number. For more engineering and market research notes, join Alpha Signal on Telegram.