Hacker News Reader

Comment by chucky_z | Hacker News Reader

I am currently on this train.

Having used rkt in the past, I went to revisit it recently only to find this: https://www.cncf.io/blog/2019/08/16/cncf-archives-the-rkt-pr...

I am so extremely disappointed in the CNCF as rkt (at the time, at least) seemed to be more "production ready" than Docker.

Are there any real alternatives? Is the answer "find something else that uses containerd in a more friendly way?" Is the answer "try to use podman/buildah, which are weird in their own way?"

View on HN

Podman looks interesting at a quick glance, though not supporting docker-compose makes migrating nontrivial for us.

It was discussed recently in the podman Github issues that this functionality will be covered by the separately maintained podman-compose, which was recently transferred here:

https://github.com/containers/podman-compose

and my attempt to get it run on mac were fruitless. I would have to do it in a Vagrant VM like 5 years ago.

Wasn't that because RedHat bought CoreOS, and RH is all k8s? And then no one was pushing rkt along with commercial support, so it died?

Agree the rkt was cool. I just don't know if RH is becoming more like MSFT or more like Oracle.

More like IBM it seems :)

Maybe containerd [0] is an alternative? It's being used in k3s instead of Docker.

[0]: https://containerd.io/

edit: I didn't notice that you mentioned this in your comment, my bad. Can you explain why it doesn't work for you? I'm new to the Docker-alternative scene and thought it looked pretty good at first glance.

Docker uses containerd.

Here's an image straight from a blog post from last year: https://i1.wp.com/blog.docker.com/wp-content/uploads/2018/09...

https://blog.docker.com/2018/09/join-the-beta-for-docker-eng...

It does and it doesn't. The interface is pretty different. Using containerd directly as a binary is pretty rough around the edges, but docker uses it as a library. In particular the CRI implementation works, but leaves a lot to be desired. Their release cycle is also pretty lengthy, such that each minor release has a ton of changes, resulting in a lot of work to integrate into your infra.

We're implementing CRI-O so we can use Docker and Kata Containers side by side for different workloads. We're hoping if things go well we can fully migrate off Docker after a few years of transition, but it's in early stages.

Reply on news.ycombinator.com