15 ms·
I like the docker way of one thing, one process, per container. LXC seems a bit different. However, an exciting thing to me is the Cambrian explosion of altern
by adamgordonbell 5y ago
I like the docker way of one thing, one process, per container. LXC seems a bit different.
However, an exciting thing to me is the Cambrian explosion of alternatives to docker: podman, nerdctl, even lima for creating a linux vm and using containerd on macos looks interesting.
- merlinscholz 5y agoI recently started using containerd inside Nomad, a breath of fresh and simple air after failed k8s setups!
- adamgordonbell 5y agoOh, Nomad looks interesting. Why should someone reach for it vs K8S?
- dijit 5y agoNomad can run a lot more things but it’s not so batteries included. Nomad is trying to be an orchestrator. Kubernetes is trying to be an operating system for cloud environments. since they aim for being different things they make different trade offs.
- orthecreedence 5y agoI have used nomad at my work for a few years now. I'd say where it shines is running stateless containers simply and easily. If you're trying to run redis, postgres, etc...do it somewhere else. If you're trying to spin up and down massive amounts of queue workers hour by hour, use it as a distributed cron, or hell just run containers for your public api/frontend and keep them running, nomad is great. That said, you're going to be doing some plumbing for things like wiring your services together (Fabio/Consul Connect are good choices), detecting when to add more host machines, etc. As far as how it compares to k8s, I don't know, I haven't used it materially yet.
- merlinscholz 5y agoCloudflare recently posted a great blog article on how/why they use nomad: https://blog.cloudflare.com/how-we-use-hashicorp-nomad/ https://blog.cloudflare.com/how-we-use-hashicorp-nomad/
- umvi 5y agoDocker can have N processes per container though, just depends how you set up your image
- trulyme 5y agoYes, and it makes sense in some cases. Supervisord is awesome for this.
- wanderr 5y agoThat seems weird for some stacks though, like nginx, php-fpm, php. At least I still haven't wrapped my head around what's the right answer for the number of containers involved there.
- cpuguy83 5y agoIt is workload dependent. My general way of thinking about it is containing a unit of work. Sometimes that is a single process, others it is a bunch of things. Sometimes I may want to run a database separate from my application code, sometimes not. How do you scale it, how do you manage it, how will it get deployed, all questions that go into the answer of what should go into it.