4 ms·

The problem for docker is that just by building docker engine, they don't really have a way to make money – so stuff like this is probably all an attempt to act

by atonse 10y ago

The problem for docker is that just by building docker engine, they don't really have a way to make money – so stuff like this is probably all an attempt to actually have differentiating products that can generate revenue.

hosh 10y ago
Yep, and CoreOS and Kubernetes are already moving towards Rocket as the default, underlying engine.
- zwischenzug 10y ago
  Kubernetes? Really? Any evidence?
  - hosh 10y ago
    https://github.com/kubernetes/kubernetes/issues/2725 https://github.com/kubernetes/kubernetes/issues/2725 https://docs.google.com/document/d/1dYxInIUDTm4HEArQ9Hom_1NhYw22WrXWdglnaLjtQsI/edit#heading=h.2mzw2mutm6lx https://docs.google.com/document/d/1dYxInIUDTm4HEArQ9Hom_1Nh... I should clarify: CoreOS + Kubernetes using rocket by default. From what I understand, CoreOS is driving the effort to get rocket supported by Kubernetes. K8S looks like it is going for agnostic implementation.
    - sbt 10y ago
      Yes. Also note that CoreOS is basically a shell corporation for Google.
    - smarterclayton 10y ago
      There is a log of emphasis going on in Kube right now in making sure that there is lots of room for experimentation around container formats, tools, and architectures - while at the same time, trying to keep Docker working well at scale and introducing Rktnetes. There's also work being done around runc support and VMs (from the hyper guys). Ultimately containers are just processes (some of them kernels), images are just another archive format, and the glue is what makes them interesting. Disclaimer - I work on Kubernetes
      - zwischenzug 10y ago
        Hi Clayton, intrigued by this: '(some of them kernels)' - are you alluding to unikernels (among others)?
gtirloni 10y ago
I don't think this is an attempt by Docker to sell tools to make money. They are improving their ecosystem to make their company more relevant which may or may not snowball into other companies actually paying for their services (Docker Cloud, etc). Few companies are investing in making money by selling tools. Instead, you see Google/Amazon/Microsoft improving their cloud offerings and hoping you will your money there. They are giving away their tools (Kubernetes, Visual Studio, etc) hoping their environments become more attractive to you. I hope we are not repeating history with the "DAB" the same way the container spec in the past. The industry is tired of these format fights and we need standardization to move things forward. I would put more faith in the "DAB" format if it was announced as something coming from the CNCF or similar. During the keynote the Atomic Nulecule [1] format came to mind... I don't know how it compares but it looks similar. 1 - https://github.com/projectatomic/nulecule https://github.com/projectatomic/nulecule

by atonse 10y ago

hosh 10y ago

Yep, and CoreOS and Kubernetes are already moving towards Rocket as the default, underlying engine.

zwischenzug 10y ago
Kubernetes? Really? Any evidence?
- hosh 10y ago
  https://github.com/kubernetes/kubernetes/issues/2725 https://github.com/kubernetes/kubernetes/issues/2725 https://docs.google.com/document/d/1dYxInIUDTm4HEArQ9Hom_1NhYw22WrXWdglnaLjtQsI/edit#heading=h.2mzw2mutm6lx https://docs.google.com/document/d/1dYxInIUDTm4HEArQ9Hom_1Nh... I should clarify: CoreOS + Kubernetes using rocket by default. From what I understand, CoreOS is driving the effort to get rocket supported by Kubernetes. K8S looks like it is going for agnostic implementation.
  - sbt 10y ago
    Yes. Also note that CoreOS is basically a shell corporation for Google.
  - smarterclayton 10y ago
    There is a log of emphasis going on in Kube right now in making sure that there is lots of room for experimentation around container formats, tools, and architectures - while at the same time, trying to keep Docker working well at scale and introducing Rktnetes. There's also work being done around runc support and VMs (from the hyper guys). Ultimately containers are just processes (some of them kernels), images are just another archive format, and the glue is what makes them interesting. Disclaimer - I work on Kubernetes
    - zwischenzug 10y ago
      Hi Clayton, intrigued by this: '(some of them kernels)' - are you alluding to unikernels (among others)?

gtirloni 10y ago

I don't think this is an attempt by Docker to sell tools to make money. They are improving their ecosystem to make their company more relevant which may or may not snowball into other companies actually paying for their services (Docker Cloud, etc). Few companies are investing in making money by selling tools. Instead, you see Google/Amazon/Microsoft improving their cloud offerings and hoping you will your money there. They are giving away their tools (Kubernetes, Visual Studio, etc) hoping their environments become more attractive to you. I hope we are not repeating history with the "DAB" the same way the container spec in the past. The industry is tired of these format fights and we need standardization to move things forward. I would put more faith in the "DAB" format if it was announced as something coming from the CNCF or similar. During the keynote the Atomic Nulecule [1] format came to mind... I don't know how it compares but it looks similar. 1 - https://github.com/projectatomic/nulecule https://github.com/projectatomic/nulecule