3 ms·
Docker's main focus is to "get people agree on something". And they are doing great in getting traction and adoption. But if everyone starts to create their own
by bastichelaar 12y ago
Docker's main focus is to "get people agree on something". And they are doing great in getting traction and adoption. But if everyone starts to create their own flavor of containers, we still don't get portability across servers and clouds. It would be better IMHO if Rocket implements the Docker API, or if they collaborate together in creating a minimal standard. Then everyone would benefit. I'm really curious how Solomon will respond to this...
- philips 12y agoFWIW, part of the design difference is that rocket doesn't implement an API. When you do `rkt run` it is actually executing under that PID hierarchy; there is no rktd that forks the process. This is a design goal so that you can launch a container under the control of your init system or other process management system.
- lambdaops 12y agoThat's really too bad, because the only way for me to spawn containers programmatically is shelling out.
- cbsmith 12y agoForking, not shelling out, no?
- thockingoog 12y agoThis was a key principle of LMCTFY, too, FWIW.
- deleted 12y ago[deleted]
- fss 12y agoIn case you change your mind, I just created this awesome project: https://github.com/fsouza/go-rocketclient https://github.com/fsouza/go-rocketclient
- otoburb 12y agoDocker's initial response: https://blog.docker.com/2014/12/initial-thoughts-on-the-rocket-announcement/ https://blog.docker.com/2014/12/initial-thoughts-on-the-rock...
- bastichelaar 12y agoThanks!