News for hackers. Stuff that matters.

A comment on Docker in Production: A History of Failure. Parent comment

Re:Docker in Production: A History of Failure by fpoling on Friday November 04, 2016 @01:14PM (#12874183)
What is wrong with DB in container? As long as one uses host volumes for persistent data, docker allows to isolate DB setup rather nicely.
[ Parent | on HN ]
Re:Docker in Production: A History of Failure by blorenz on Friday November 04, 2016 @02:09PM (#12874611)
Agreed and confused. Interested to find what would be wrong with this? (from my docker-compose.yml under the db service) volumes: - ./data/postgresql:/var/lib/postgresql/data
[ Parent | on HN ]
Re:Docker in Production: A History of Failure by adenot on Saturday November 05, 2016 @01:38AM (#12878356)
Reverse question that no-one seems to ask: What's the advantage of running a DB on a container?
[ Parent | on HN ]
Re:Docker in Production: A History of Failure by etherealG on Wednesday November 09, 2016 @03:43AM (#12907985)
Spinning a new db in continuous integration for integration tests.
[ Parent | on HN ]
Re:Docker in Production: A History of Failure by eggie5 on Friday November 04, 2016 @02:07PM (#12874599)
Yeah I'm wondering this too...
[ Parent | on HN ]
Re:Docker in Production: A History of Failure by tzaman on Friday November 04, 2016 @03:00PM (#12875004)
Read my reply below
[ Parent | on HN ]