Copy-on-Write (CoW) Explained: OS and Docker

If you’ve ever heard the term Copy-on-Write (CoW) and thought it sounds like some deep technical wizardry, don’t worry. It’s actually a simple and smart trick used in both Operating Systems and Docker to save time and resources. Let’s break it down in plain English.

What is Copy-on-Write?

Normally, when you copy something in a computer (like memory or a file), the system makes a full copy right away.

But most of the time, that copy isn’t even changed.

Copy-on-Write (CoW) says:

“Don’t copy until someone actually changes it.”

• Both the original and the copy share the same data.
• A new copy is made only when a modification happens.

This way, the system avoids wasting memory, disk, and time.

Copy-on-Write in Operating Systems

In OS, CoW shows up when we use the fork() system call.

• When a process calls fork(), the OS creates a child process.
• Instead of duplicating the entire memory space of the parent:
  • The parent and child share the same memory pages.
  • If either process tries to write to a page, then the OS makes a private copy for that process.

Benefits:

• Faster process creation (no full copy at fork time)
• Lower memory usage (unchanged pages are shared)

Copy-on-Write in Docker

Docker uses CoW at the filesystem level.

• Docker images are made of layers (e.g., Ubuntu base → libraries → app code).
• When you start a container:
  • It gets a read-only view of the image layers.
  • A small writable layer is added on top.
• If the container changes a file:
  • Docker doesn’t touch the original image.
  • Instead, it copies that file into the writable layer and applies changes there.

Benefits:

• Multiple containers share the same base layers → saves disk space
• Containers start quickly (no heavy copying)
• Isolation (changes in one container don’t affect others)

A Simple Analogy

Think of it like sharing a Google Doc:

• Everyone sees the same document at first.
• If you just read it, nothing is copied.
• If you edit it, Google gives you your own private version so you don’t mess with the original.

That’s exactly how CoW works.

Conclusion

Copy-on-Write (CoW) is a smart trick that makes systems more efficient:

• In Operating Systems, it speeds up process creation and reduces memory usage.
• In Docker, it makes containers lightweight, fast, and isolated.

So next time you spin up a Docker container or run a fork(), remember:

you’re benefitting from the magic of Copy-on-Write.

by Harshit Kumar
DiCoTr