Episode 71: Unbreakable Docker, or, elephants, er, like other elephants

Published: Sept. 2, 2016, 3 p.m.

Eventually, you have to decide how your open source software is going to make money, and your partners probably won\u2019t like it. That\u2019s what the dust-up around Docker is this week, it seems to us. We also talk briefly about VMware\u2019s big conference this week, and rumors of HPE selling off it\u2019s Software group to private equity.

\n\n

Listen above, subscribe to the feed (or iTunes), or download the MP3 directly.

\n\n

With Brandon Whichard, Matt Ray, and Coté.

\n\nSPONSOR\n\n\n\nShow notes\n\n
    \n
  • Nippers - "Nippers learn about safety at the beach. They learn about dangers such as rocks, and animals (e.g. the blue-ringed octopus), and also about surf conditions, such as rip currents, sandbars, and waves. Older Nippers also learn some basic first aid and may also learn CPR when they reach the age of 13."
  • \n
\n\nCan someone explain this \u201cDocker forking\u201d hoopla?\n\n
    \n
  • Cot\xe9\u2019s write-up.
  • \n
  • Docker Inc. doesn\u2019t want to be a commoditized building block\nFrom a Red Hat person: \u201cThe conflict started to escalate earlier this summer, when Docker Inc used its controlling position to push Swarm, it\u2019s own clone of Kubernetes-style container orchestration, into the core Docker project, putting the basic container runtime in a conflict with a notable part of its ecosystem. Docker Inc. then went on to essentially accuse Red Hat of forking Docker - at the Red Hat Summit no less. After that, Docker Inc\u2019s Solomon Hykes came out strongly against the efforts to standardize the container runtime in OCI - an initiative his company co-founded.\u201d
  • \n
  • Re: that episode where we discuss Docker ecosystem challenges: \u201cYet on a regular basis, Red Hat patches that enable valid requirements from Red Hat customer use cases get shut down as it seems for the simple reason that they don\u2019t fit into Docker Inc\u2019s business strategy.\u201d
  • \n
  • A fight over where to draw the line between free/open/commodified and costs/proprietary/competitive: "And while I personally consider the orchestration layer the key to the container paradigm, the right approach here is to keep the orchestration separate from the core container runtime standardization. This avoids conflicts between different layers of the container runtime: we can agree on the common container package format, transport, and execution model without limiting choice between e.g. Kubernetes, Mesos, Swarm."
  • \n
  • Don't bring a pistol to a bazooka fight. Enterprises love RHEL - have you ever tried to sell Ubuntu into organizations? It\u2019s like what selling NT must have been like.
  • \n
\n\nVMware hybrid cloud solutionaring\n\n\n\nThis Week in Tech Private Equity\u2026\n\n\n\nBONUS LINKS! Not covered in podcast.\n\nSpaces vs. Tabs\n\n\n\nRecommendations\n\n