DEV Community

Alex Georghiou
Alex Georghiou

Posted on

What Docker Solves and What It Does Not

What Docker Solves and What It Does Not

Containers made reproducible deployment much less painful. They did not make bad applications reliable.

A container can package a runtime and its dependencies, but it cannot decide when your application is actually ready for traffic. A process may be running while migrations are incomplete, downstream connections are unavailable, or a background initialization task is still warming up.

I separate three concepts: the process is alive, the process is ready, and the service is healthy enough to perform its advertised work. These signals should not be collapsed into one HTTP endpoint that always returns 200.

Image size matters, but operational behavior matters more. Does the process handle termination signals? Does it finish or abandon in-flight requests safely? Are logs sent to standard output? Is configuration injected at deployment instead of baked into the image?

A good image is boring: reproducible build, minimal runtime dependencies, non-root execution where feasible, and no secrets inside layers. A good service is similarly boring: explicit health semantics, bounded startup, and graceful shutdown.

Containers simplify delivery. They do not remove the need to understand lifecycle, state, or failure.

Top comments (0)