> That's why you have staging (you do have staging, right?).
Plenty of people don't. The main reason being that staging is never quite the same as production...
We are working in a remote team, so replicating shared envs locally is important. Our system contains multiple databases, application servers, SMTP, etc etc. -- you can use all of them in your local dev env. It's not the same as prod because of different latencies, etc., but all containers are present locally. It is _very_ useful.
Re:What’s New in Docker 1.13?
by crdoconnor on Friday January 20, 2017 @10:03AM
(#13444269)
>We are working in a remote team, so replicating shared envs locally is important.
It is, but I'm not particularly keen on docker as a solution to this problem. It provides a low level of isolation/realism for these services and the tooling surrounding it is relatively poor.
Re:What’s New in Docker 1.13?
by bradmwalker on Friday January 20, 2017 @10:03AM
(#13444262)
What about LXC system containers? Differences between hardware and OS virtualization still exist, e.g. immutable system clock, but it's otherwise like running a regular Linux box. An init process that can simulate rebooting, mature system package management, no process isolation that's often gratuitous, etc.
Re:What’s New in Docker 1.13?
by bradmwalker on Friday January 20, 2017 @10:03AM
(#13444263)
What about LXC system containers? Differences between hardware and OS virtualization still exist, e.g. immutable system clock, but it's otherwise like running a regular Linux box. An init process that can simulate rebooting, mature system package management, no process isolation that's often gratuitous, etc.
It's better to make the environment as close as possible to prod without adding massive inconvenience but docker both adds inconvenience and forces you to use it in production (which entails a whole other set of headaches) if you want close environmental parity, and even then, since it's lightweight virtualization there are hundreds of things which can behave differently between dev and prod.
IMHO you either want very close environmental parity (in which case full virtualization is the way to go) or you don't, in which case running locally is fine.