Hey Trenton, it seems you misunderstood humility and networking with other humans.

I suggest reading ahead to the portion that covers production builds:
https://hackernoon.com/a-tale-of-two-docker-multi-stage-build-layers-85348a409c84

Listen — development and production are not the same.

They just aren’t.

You are confusing the ability to run the production Dockerfile everywhere with needing to run it everywhere.

In development, you use different tools, such as hot module reloading. You run on a mac instead of Alpine Linux. You run with npm instead of node directly. Docker most certainly supports volume mounts as I use them in the above example. We don’t have a Dockerfile in this example so there isn’t even a place to do “layer caching”.

Again, check out the portion of the series that covers production Dockerfiles for that.

You can most certainly run your production Dockerfile locally and it will run the same way as production but let’s not pretend development and production are the same environments. They aren’t and making them the same was never the purpose.