docs: first pass comparing rkt to other projects #1588
Conversation
|
||
## rkt vs Docker | ||
|
||
The Docker Engine, or simply Docker, is an application container runtime system that runs as a centralized API daemon. Docker can take `a "Docker Image" name, such as `quay.io/coreos/etcd`, and download, execute, and monitor the application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Docker can take `a /Docker can take a/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "Docker Image" link to the Docker Image Specification?
"Docker Engine" (with a capital E)? |
runC does not have a centralized daemon, and, given a properly configured "OCI bundle", can be integrated with init systems such as upstart and systemd. | ||
|
||
rkt includes the same functionality as runC but does not expect a user to understand low-level details of the operating system to use, and can be invoked as simply as `rkt run coreos.com/etcd,version=v2.2.0`. | ||
It can download both "Docker Images" and "Application Container Images". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can download both Docker Images and Application Container Images.
@alban thanks for the review, addressed all your comments I think |
The document mentions After that, LGTM! |
docs: first pass comparing rkt to other projects
No description provided.