Docker acquires Kitematic

#1

Post by alexkappa » Thu, Mar 12, 2015, 1:52 PM UTC

Docker acquires Kitematic
blog.docker.com

Re: Docker acquires Kitematic

#2

Post by jamescun » Thu, Mar 12, 2015, 2:06 PM UTC

For a company who is "not trying to own the ecosystem" - they sure are buying a lot of the ecosystem.

Re: Docker acquires Kitematic

#3

Post by josephjacks » Thu, Mar 12, 2015, 2:06 PM UTC

Interesting acquisition that proves graphical mgmt of containers is an important part of the UX.

Re: Docker acquires Kitematic

#4

Post by josephjacks » Thu, Mar 12, 2015, 2:09 PM UTC

jamescun wrote: post #2

For a company who is "not trying to own the ecosystem" - they sure are buying a lot of the ecosystem.

Docker is trying to be the center of the universe, just as SAP tries to do so beyond core applications with integration, monitoring, BI, systems, etc... Perhaps in the very long run this strategy could pay off, but I believe a lot of valuable companies will be created that focus on the gaps and really nail them in a focused manner.

Re: Docker acquires Kitematic

#5

Post by jonesetc » Thu, Mar 12, 2015, 2:12 PM UTC

jamescun wrote: post #2

For a company who is "not trying to own the ecosystem" - they sure are buying a lot of the ecosystem.

Eh, kitematic doesn't really do much in my experience, it's just a GUI over docker. It's just one of those things where they would have eventually made a GUI anyway, why not just try to grab the best one at the moment if they can?

It also doesn't feel like owning the ecosystem to me because someone else could (and I'd wager that a handful will) make a new GUI that becomes more popular than kitematic.

Re: Docker acquires Kitematic

#6

Post by josephjacks » Thu, Mar 12, 2015, 2:13 PM UTC

jonesetc wrote: post #5

jamescun wrote: post #2

For a company who is "not trying to own the ecosystem" - they sure are buying a lot of the ecosystem.

Eh, kitematic doesn't really do much in my experience, it's just a GUI over docker. It's just one of those things where they would have eventually made a GUI anyway, why not just try to grab the best one at the moment if they can? It also doesn't feel like owning the ecosystem to me because someone else could (and I'd wager that a handful will) make a new GUI that becomes more popular than kitematic.

+1

Re: Docker acquires Kitematic

#7

Post by pearjuice » Thu, Mar 12, 2015, 2:13 PM UTC

I thought Docker wanted to be "just Docker" and not leverage all the tools and stacks which can or cannot be used with Docker? There is absolutely nothing wrong with the fist, but I am pretty sure Docker was pushing itself as "just Docker". All their latest acquisitions don't really reflect the image they want to portray.

Re: Docker acquires Kitematic

#8

Post by moondowner » Thu, Mar 12, 2015, 2:34 PM UTC

Just checked out the source of Kinematic https://github.com/kitematic/kitematic

Nice use of atom-shell and React.

Re: Docker acquires Kitematic

#9

Post by imescent » Thu, Mar 12, 2015, 2:54 PM UTC

jamescun wrote: post #2

For a company who is "not trying to own the ecosystem" - they sure are buying a lot of the ecosystem.

If you read between the lines "not trying to own the ecosystem" is just business talk for "we want ya'll to feel safe about buying into the thing we've built, so at the end of the road when we own the ecosystem, the checks go out to us". There's nothing wrong with that, as long as you understand what they mean.

Remember that Docker is a funded business, that has an obligation to its investors.

Re: Docker acquires Kitematic

#10

Post by torkalork » Thu, Mar 12, 2015, 2:55 PM UTC

Definitely some neat features here which will help people who need to use Docker but can't use the command line.

For example, when you click the 'Terminal' button on a running container, it automatically starts a docker-exec command in that container for you, which is handy.

For people checking it out today, note that it creates its own boot2docker VM, even if you have one on your system already. So Kitematic won't be able to see any of the images or containers you have running through your other boot2docker VM.