If you think of rkt as an analogy to `apt-get` I think it makes a bit more sense. apt-get has methods for downloading and installing software over the internet

If you think of rkt as an analogy to `apt-get` I think it makes a bit more sense. apt-get has methods for downloading and installing software over the internet. Similarly, rkt has methods for downloading and running container images. And like apt-get rkt doesn't build packages but relies on a spec and a build system. rkt also avoids being an init system. This allows for rkt to be used with existing init systems for things like system services, daemons, etc. It also means that you can use rkt containers alongside your "normal" init tooling.