Well, there&#x27;s a couple of scenarios:<p>- Long-running processes where they don&#x27;t want to destroy and redeploy every single time a fix or change gets deployed<p>- One is where they try to reduce the configuration sprawl by making configuration changes at runtime using something like ansible<p>- One is straight-up bigco stupidity (we must have a way to change the running configuration of a system because the audit team says so)<p>- separation of responsibilities - we have one team that builds &quot;approved&quot; docker images, and then dev teams can make changes based on that - it might be easier to deploy changes at launch time<p>Again, I&#x27;m not saying all of these make sense, but back when I was workign on docker strategy and interviewing really big companies, these are the types of concerns they had about implementing docker at scale.