News for hackers. Stuff that matters.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by vacri on Thursday April 14, 2016 @01:57AM (#11494576)
We were using docker up to about a year ago, and ripped it out for just this reason - we didn't have the time available to keep coding the workarounds. Great if you have the time, not so great if you don't.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by endymi0n on Thursday April 14, 2016 @02:52AM (#11494752)
We were too deep in already unfortunately, but 1.10 introduced a whole new barrage of bugs and regressions, wasting hours and days working around it. If they don't devote some time getting the basics right and getting the core stable, we need to really consider alternatives. I'm already scared what 1.11 will break.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by cpuguy83 on Thursday April 14, 2016 @09:29AM (#11496470)
Please make sure to report any issues so they can be fixed.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by crdoconnor on Thursday April 14, 2016 @04:36AM (#11495102)
Stuff like this is what makes me wary of any technology that's been hyped.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by yomism on Thursday April 14, 2016 @06:59AM (#11495588)
I too had a production deploy using Docker and but droped it because of changes like this and some instability.

Started using Ansible (ok, maybe comparing oranges to apples here) and its better for my use case.