2 ms·
And then there was rkt around the same time as Docker and thought they would be able to take the mantle when Docker-the-company struggled to make money. The big
by hinkley 4y ago
And then there was rkt around the same time as Docker and thought they would be able to take the mantle when Docker-the-company struggled to make money. The biggest problem with that theory is that it had none of this secret sauce you mention.
When I would point this out I usually got brigaded. Now RedHat owns the company that made rkt and I don't know if it's even being developed anymore. But nobody brings it up so I don't even have to think about it.
- theamk 4y agorkt (and many other container solutions) was introduced after docker was released and became popular... they even mentioned docker's shortcomings as a motivation for the project creation [0]. It had all the same problems as other replacement software: there were plenty of bugs and missing features (the announcement mentions "prototype quality release"), documentation was limited, and there are no community to help you. None of those would be fatal if it was significantly better than docker, but it was not -- it had less functionality and needed more scaffolding. So almost no one made the switch. It is closed now [1] And why "rkt"? There were much better alternative container runtimes. For example Sylabs Singularity [2] -- container-as-a-file, instant mounting, etc... I wish more people knew about it. [0] https://web.archive.org/web/20141201181834/https://coreos.com/blog/rocket/ https://web.archive.org/web/20141201181834/https://coreos.co... [1] https://github.com/rkt/rkt#warning-end-of-project-warning https://github.com/rkt/rkt#warning-end-of-project-warning [2] https://github.com/sylabs/singularity#singularityce https://github.com/sylabs/singularity#singularityce