Hacker News Reader

There's no conflict between using Docker for CI (and deployment) and not using Docker for development.

Oh ok, so they still build and maintain a (fragile?) docker image with up to date build tooling for CI machines to use?

I cannot speak for the OP, but this is more or less how we use Docker at my workplace.

> (fragile?)

The Docker image isn't fragile, it's your software that risks becoming fragile if it's too strongly reliant on a specific environment.

Oh I see what they mean now. Lack of varied developer preference leads to things like hard coded paths instead of configuration files, for example.

It’s been rare, but this has definitely been a problem: “Why do I need an ENV var, the path is always /app?” And then not supporting symlinks... ugh.

Reply on news.ycombinator.com