News for hackers. Stuff that matters.
Re:Docker in Production: A retort by kstenerud on Saturday November 05, 2016 @03:24PM (#12881414)
I'm still not sure I follow. If you're not setting up a DB that will have such heavy usage that it needs bare metal access, what's wrong with setting it up such that it stores data on a NAS, or via mounted volumes? Then when it comes time to upgrade due to a security issue, you can create a new container, spin it up, and if it barfs, relaunch the old one.
Re:Docker in Production: A retort by toomuchtodo on Saturday November 05, 2016 @03:37PM (#12881482)
Unnecssesary complexity. A VM would've sufficed for what you described.
Re:Docker in Production: A retort by distracted_boy on Saturday November 05, 2016 @05:56PM (#12882121)
What is the "Unnecssesary complexity" in this scenario? You literally just run a command and you can spin up a new container with your data.
Re:Docker in Production: A retort by cs02rm0 on Saturday November 05, 2016 @03:55PM (#12881561)
I find VMs are super slow for development purposes (I mean setup, starting up and shutting down rather than actual processing), where docker's made a massive difference. YMMV especially if you're not spinning up new projects frequently.

They might be a better solution in production, but I have a strong preference for production mimicking development.

Re:Docker in Production: A retort by ascendantlogic on Saturday November 05, 2016 @04:06PM (#12881615)
Precisely the point. It's fine in dev but once you are running in prod and need rock solid stability the generally accepted dogma is that containerizing your DB is playing with fire. As you said, YMMV.