Hacker News Reader

> hard to debug

When I started using Docker four years ago that was my biggest issue. When builds fail, I can't just pick up where it left to expect the environment and try stuff out (unless I purposely build an image with a ton of layers).

Soooo much time was wasted figuring out what was going on.

View on HN

Not to be reductive, but why not `docker run` the sha256 of the last successful stage of the build and run the next command manually?

That's what I generally do, but it's tedious as CI images are written to have as few layers as possible. So debugging often also involves changing Dockerfiles.

Reply on news.ycombinator.com