News for hackers. Stuff that matters.
Re:Docker not ready for primetime by siliconc0w on Sunday August 28, 2016 @03:54PM (#12378198)
We see a couple of different bugs that are best solved by simply rebuilding the container host. To docker's credit these tend to decrease with high versions.

We also see them mostly in non-prod environments where we have greater container/image churn. We use AWS autoscale and Fleet so containers just get moved to other hosts when we terminate them. We have actually thought about scheduling a logan's run type job that kills older hosts automatically - it's in the backlog.

Re:Docker not ready for primetime by majewsky on Monday August 29, 2016 @05:30AM (#12380874)
Bugs that can be solved by a rebuild are not restricted to Docker. We had an interesting week when the build was red all the time for various reasons, and then prod started failing. Usually we deploy once a day, and not deploying for a week caused several small memory leaks to turn into big ones.