1. [Comment removed by author]

        1. 1

          It is ironic that they’re launching themselves circa 2011 as a product! EC2 classic FTW.

          1. 2

            This also goes hand-in-hand with an argument around core competencies. I’ll stick my neck out here and say that, for most, running a timeseries database for telemetry is outside of your core competency. Running a CI system is outside your core competency. Arguably running your data store is outside of your core competency.

            1. 1

              I can’t be the only one who finds Docker in and of itself entirely uninteresting. It should be a commodity in the UNIX vein, something that is orthogonal to Docker the company I suspect. Container orchestration I can get very excited about. Container orchestration plus Criu even more-so.

              @rfisher makes a good point when comparing Linux containers to a decade of Solaris and its offspring: in the latter the support is pervasive. In Linux it is tacked on.

              Friends of mine in the S/390 and AS/400 world must be laughing into their LPARs and ASPs at the hurdles Linux containerization is putting in front of itself. That said, I don’t have a support contract thumping onto the mat once a year.

              In terms of Docker the company the one thing I found out from my daliance with an alliance with Opscode is that monetizing open-source infrastructure software is nigh-on impossible. In terms of consulting you’re between a bunch of incumbent beards who wouldn’t do it any other way than their own and at the other end stultified multi-nationals who really only want to train their own staff. And hence Opscode/Chef are now a shop selling compliance training. I can see the same thing happening to Docker Inc.