I've not played with containers yet, but the concept sounds interesting.

The use cases for development / QA types systems is fairly easy to see, but for a production environment I'm having a hard time coming up with a case where it would be worth the time / effort to get things set up.  About the only situation I've been able to think of would be some sort of reporting type application.
Set it up so that every morning, or whenever, it creates a SQL container with a blank DB, pulls in the required data from the production SQL instance on another server, then holds the data for the reporting application until the user is done (could be all day, could be a couple hours, whatever.)  The user would be able to generate reports, even if not connected to the network, without impacting the production data.  The user could even modify the data, again without impacting the production data (although if they generate reports and play with the data on a production instance, you might need to re-think your process anyways...)

But even there, why not just stand up an Express instance on their device?  Less headache, and probably about as much work initially...