4 ms·
Kubernetes is used for orchestrating containers. Pods are used for optimizing hardware resources. As far as I know, Docker have zero support for neither. Edit:
by AtNightWeCode 5y ago
Kubernetes is used for orchestrating containers. Pods are used for optimizing hardware resources. As far as I know, Docker have zero support for neither.
Edit: Please tell me down voter how to do this with Docker..
- amarshall 5y agoHuh? Docker 100% supports containers. I mean, it’s sort of the whole point. There’s even an example in the article.
- AtNightWeCode 5y agoContainer orchestration. Look it up. Edit: Lol @ comments. ...could mean... I don't think anybody talks about orchestrating containers without meaning it includes scheduling and so on. What Kubernetes, Nomad, Service Fabric and so on does. The tools we use. We can include Docker Swarm for courtesy if you want...
- amarshall 5y agoOrchestration could mean a variety of different things. Distributed multi-machine orchestration? No. Orchestration of containers on one machine? Sure, though one could argue that Compose or Swarm is needed for that.
- AtNightWeCode 5y agoNo, not really if you work in the field of containers.
- bluedays 5y agoOh, the container software Docker isn't used to create containers? TIL
- AtNightWeCode 5y agoDocker is used to run containers. Not orchestrating containers. Wow, seems to be language barrier here. :) Edit: Nothing in the article mentions Docker Swarm you sillies..
- yjftsjthsd-h 5y agoDocker still ships with swarm compiled in, so yes, actually, docker does orchestrate containers.
- jrockway 5y agoDocker is a brand name for a bunch of totally unrelated concerns. It's some metadata attached to some tar archives. It's a repository that hosts said tar archives and metadata. It's a client for pushing and pulling said archives. It's a container runtime. It's a cgroups manager. It's a networking layer. It's a container orchestrator. It's a Mac app that requires you to pay them to run a Linux VM. They do a shit ton of stuff and named their product and their company the same thing, and were here pretty early on. My point is that it's a largely useless term. If you want to understand things at a deeper level, you have to cut through the cruft. You can put linux distributions into tar files and run them without Docker (see systemd-nspawn). You can use cgroups to run ordinary Linux binaries. You can make a group of processes run on a fake private network. You can build OCI-compliant container images without ever running a single thing in a container. Docker conflates all of this and confuses people. Don't be confused, realize that "Docker" does a lot.
- gizdan 5y agoDocker doesn't do pods, pods are just a collection of containers. Docker's whole thing is containers plus some enterprise tooling on top of it. Pods are the smallest deployable units in Kubernetes. No one said Docker supports pods, but Docker definitely, 100%, supports containers, it's literally the thing that it's known for.
- AtNightWeCode 5y agoRead the article
- deleted 5y ago[deleted]
- cvzu 5y agoYou need to be more concise when posting or you will get down voted
- moondev 5y agoOf course you can create pods with docker, run it along with kubelet and drop manifests into /etc/kubernetes/manifests. This is what static pods are