In Unix-like systems such as Ubuntu and macOS, storage devices go by names like disks, partitions, volumes, images, containers, and drives. Windows employs a similar vocabulary with subtle variations. As a systems administrator with extensive experience across these platforms, I've seen how mastering these terms simplifies troubleshooting and management. Here's a clear breakdown of drive, disk, partition, volume, image, and containers.

A drive represents the primary storage hardware unit recognized by your operating system—think hard disk drives (HDDs), solid-state drives (SSDs), or USB drives. In Windows, drives are often labeled with letters like C: or D:, serving as entry points to underlying disks and volumes.
The disk is the complete physical storage medium within a drive, such as the platters in an HDD or NAND flash in an SSD. Operating systems identify disks by cryptic identifiers like /dev/sda in Linux or disk0 in macOS Disk Utility. Disks form the foundation, holding one or more partitions.
A partition closely resembles a volume but refers strictly to a carved-out portion of a disk, defined by size in the partition table. It doesn't require a filesystem or formatting initially and can be resized (though this often risks data loss by rewriting the table). Tools like macOS Disk Utility or Ubuntu's Disks app treat unformatted partitions and formatted volumes similarly.

As a user, you interact with the volume—the formatted, mountable part of a disk or partition complete with a filesystem and user-friendly name. When you plug in a drive and see its icon in Finder or Nautilus, that's the volume. Multiple volumes reside on one disk, tracked by the OS.

A disk image is a bit-for-bit virtual snapshot of a volume or disk, stored as a file (e.g., .img, .iso) without physical hardware. Ideal for backups, Windows system images exclude empty space to save room. Mount or attach an image to access its filesystem, or clone it to another volume. Capture images from HDDs, CDs, or any volume with sufficient target space.

Containers are a macOS APFS innovation: flexible enclosures on a disk housing multiple volumes that dynamically share allocated space. Unlike rigid partitions in ext4, HFS+, or ExFAT—which fix sizes at creation and require repartitioning to resize—APFS containers allow volumes to expand or shrink seamlessly as needed.
In essence, physical disks (manifested as drives) hold partitions and volumes containing your data. APFS uses containers for flexibility, while images capture exact volume snapshots. Mastering these distinctions enhances storage handling across platforms.
Image credit: Cambridge Avaragado