8 ms·

I'm surprised to see rkt mentioned so much. This thread has a very 2017 vibe and doesn't seem to account for m(any) of the changes in Kubernetes (CRI), docker/c

I'm surprised to see rkt mentioned so much. This thread has a very 2017 vibe and doesn't seem to account for m(any) of the changes in Kubernetes (CRI), docker/containerd, anything with regard to what RH is doing as they bet more and more on this space. Anyway... Red Hat's crio is a much more obvious contender in this space (my issues with RH "marketing" of crio vs containerd aside). A slightly different scope, but even Kata's future seems more promising than rkt's. Or, just use containerd if you just want a clearly OSS engine with the weight of docker behind it. ('containerd' is Docker's container engine, effectively)

conradfr 8y ago
I cant believe people are still taking and using technologies from 2017 /s To be fair this thread is also a testament to the sad state of affair in the container industry. How can you even chose a technology confidently? It seems even more madness than the JS world. Sometimes I feel like a dinosaur with my Vagrant boxes and my dedicated server. With threads like this I feel great.
- colemickens 8y ago
  Rkt didn't get much attention in 2017 at all. I only said that because 'rkt' was often portrayed as the anti-docker years ago, and it's really no longer a good way to look at the playing field. It wasn't about making fun of rkt or anything. Also, I don't know, CRI has been in the works for ages at this point, as well as crio. It just seems like people who aren't paying attention in this space remember HN threads from 18-24 months ago where people thought rkt was going to be the savior from docker. It's just pretty out of date. The comment about vagrant and a dedicated server embody an attitude that is just depressing to me. Yes, if you stick with old, functional technologies, you won't need to pay attention and/or learn anything new. And that's fine, if you're happy with it. There's a reason the rest of us moved on. Learning about CRI and knowing that rkt is dead and crio is the alternative to containerd is not that crazy of knowledge to have, or maybe I'm underestimating how much I know in the k8s space.

conradfr 8y ago

I cant believe people are still taking and using technologies from 2017 /s To be fair this thread is also a testament to the sad state of affair in the container industry. How can you even chose a technology confidently? It seems even more madness than the JS world. Sometimes I feel like a dinosaur with my Vagrant boxes and my dedicated server. With threads like this I feel great.

colemickens 8y ago
Rkt didn't get much attention in 2017 at all. I only said that because 'rkt' was often portrayed as the anti-docker years ago, and it's really no longer a good way to look at the playing field. It wasn't about making fun of rkt or anything. Also, I don't know, CRI has been in the works for ages at this point, as well as crio. It just seems like people who aren't paying attention in this space remember HN threads from 18-24 months ago where people thought rkt was going to be the savior from docker. It's just pretty out of date. The comment about vagrant and a dedicated server embody an attitude that is just depressing to me. Yes, if you stick with old, functional technologies, you won't need to pay attention and/or learn anything new. And that's fine, if you're happy with it. There's a reason the rest of us moved on. Learning about CRI and knowing that rkt is dead and crio is the alternative to containerd is not that crazy of knowledge to have, or maybe I'm underestimating how much I know in the k8s space.