4.2.12.4 VOLUME Image Design

VOLUME image design is the consideration of when and where to declare VOLUME paths within an image, weighing the safety benefit of guaranteed default persistence against the reduced flexibility that comes with Docker enforcing a mount point automatically.

When Declaring a Volume Makes Sense

For images representing genuinely stateful services — databases, message queues, anything where losing data due to a forgotten configuration step would be a significant problem — declaring VOLUME provides a useful safety net, ensuring persistent storage happens by default.

FROM postgres:16

The official Postgres image declares its data directory as a volume specifically because losing database data due to an overlooked storage configuration would be a serious, easily avoidable problem.

When Declaring a Volume Can Be Unnecessarily Restrictive

For images where the decision of whether a given path should be persistent is more genuinely situational, an unconditional VOLUME declaration can be overly restrictive, since it forces every container to have something mounted there, even in scenarios where that might not be desired.

VOLUME /app/cache

If /app/cache is sometimes intentionally meant to be ephemeral (rebuilt fresh from a base image rather than persisted), declaring it unconditionally as a volume removes that flexibility.

Leaving the Decision to the Deployer Instead

For paths where persistence is genuinely optional or situational, it is often better to document the recommendation without enforcing it through VOLUME, leaving the actual decision to whoever deploys the image.

# /app/cache may optionally be mounted to persist cached data between runs

Testing the Practical Effect of a Volume Declaration

Before finalizing a VOLUME declaration, testing how the image behaves both with and without an explicitly provided volume helps confirm the declared default behaves sensibly in both cases.

docker run -d myapp:1.0
docker run -d -v myapp-data:/data myapp:1.0

Why Thoughtful VOLUME Design Matters

Deciding deliberately whether a given path genuinely warrants the guaranteed-mount behavior VOLUME provides, rather than applying it reflexively to every potentially persistent-looking directory, keeps an image both safe by default where it matters most and flexible where rigid enforcement would be unhelpful.