4 ms·

At Datadog we are using containerd. We've heard of other companies using cri-o. There's also a lot of mixed deployments of container vs native out there. It se

At Datadog we are using containerd. We've heard of other companies using cri-o. There's also a lot of mixed deployments of container vs native out there. It seems Kubernetes is popular but not many companies with a large number of servers are willing to bet the farm on it, so they may only run a subset of their services with it (stateless, or test environments) You can use Docker, just be ready to account for the instability. With proper detection and strategies to evict bad nodes you can build a reliable platform out of it. (though for stateful things you may end up with a real mess on your hands) Weve seen issues with cointainerd too, but at least so far it seems more stable. Basically every piece of docker is being replaced. The runtime (containerd, crio), the tools to build containers (google has several), the server to host images (ecr, gcr, etc)... it's weird to call it docker when none of the components actually use docker anymore. The gui and installer is nice for local development, so I guess it has that going for it.

ibn_ibid 8y ago
Do you have any good pointers on using containerd and building with it? I'm using Docker with the runc runtime but it still isn't the best experience.
hardwaresofton 8y ago
+1 for containerd (+ cri-containerd, which is included by default now), it's served really wonderfully (meaning I didn't have to touch it much) as the base for k8s machines I've boostrapped recently -- I don't even install Docker anymore (as in literally docker the daemon is not installed or running, just runc + containerd). The replacement of docker is a good thing IMO (though probably not a good thing for Docker the company) -- it's one of the main benefits of the kubernetes hypetrain, the development of C*I (Container <something> Interface) has been great for the ecosystem. I personally find docker's CLI way more ergonomic however.
7ewis 8y ago
How do Dockerfiles work if you aren't using Docker? Is there another way to define what the container should look like?
- cdoxsey 8y ago
  You can build the containers with Docker and ship them to a repository. The format is the same. There are also tools like jib which can build containers without docker: https://github.com/GoogleContainerTools/jib https://github.com/GoogleContainerTools/jib

ibn_ibid 8y ago

Do you have any good pointers on using containerd and building with it? I'm using Docker with the runc runtime but it still isn't the best experience.

hardwaresofton 8y ago

+1 for containerd (+ cri-containerd, which is included by default now), it's served really wonderfully (meaning I didn't have to touch it much) as the base for k8s machines I've boostrapped recently -- I don't even install Docker anymore (as in literally docker the daemon is not installed or running, just runc + containerd). The replacement of docker is a good thing IMO (though probably not a good thing for Docker the company) -- it's one of the main benefits of the kubernetes hypetrain, the development of C*I (Container <something> Interface) has been great for the ecosystem. I personally find docker's CLI way more ergonomic however.

7ewis 8y ago

How do Dockerfiles work if you aren't using Docker? Is there another way to define what the container should look like?

cdoxsey 8y ago
You can build the containers with Docker and ship them to a repository. The format is the same. There are also tools like jib which can build containers without docker: https://github.com/GoogleContainerTools/jib https://github.com/GoogleContainerTools/jib