> What is missing in my opinion is a better container backend other than Docker (I just find it not enough for more complex scenarios, too bloated, there is the PID-1-hell, etc). With the new container runtime interface I am sure this won't be a problem in the long term.
I have only been experimenting a bit with rkt, and I am very new to it, but as far as I understand it should help to address some of the points regarding the container backend, since:
1) it is just a container runtime,
2) doesn't have the client/server architecture that Docker has,
3) has a lightweight systemd starting as PID1 and reaping/adopting children, and
I have only been experimenting a bit with rkt, and I am very new to it, but as far as I understand it should help to address some of the points regarding the container backend, since:
1) it is just a container runtime,
2) doesn't have the client/server architecture that Docker has,
3) has a lightweight systemd starting as PID1 and reaping/adopting children, and
4) works with Kubernetes.
See also:
- https://coreos.com/rkt/docs/latest/devel/architecture.html
- https://kubernetes.io/docs/getting-started-guides/rkt/
- https://coreos.com/rkt/docs/latest/using-rkt-with-kubernetes...
Also note that `docker run` has an `--init` option based on `tini` which can help with the PID-1 hell.
See: https://docs.docker.com/engine/reference/run/#specify-an-ini...