> If you need Node to compile your web assets but don't need it in production, your final container doesn't need to have Node OK, I'm coming around. You could

> If you need Node to compile your web assets but don't need it in production, your final container doesn't need to have Node OK, I'm coming around. You could drop node and C compilers from your image, shedding a lot of weight. This still seems like something I'd really only want to do in production. (In a development setting, I'd like my team to be able to break into the containers and execute arbitrary commands. We should be able to, for example, "bundle update" or "assets precompile" without having a need for another separate environment to do those things. But in production, I don't want anyone running arbitrary commands or making "configuration drifts" inside of my running containers. They should be homogenous.)