Need advice about which tool to choose?Ask the StackShare community!
Docker vs rkt: What are the differences?
Developers describe Docker as "Enterprise Container Platform for High-Velocity Innovation". The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere. On the other hand, rkt is detailed as "App Container runtime". Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.
Docker and rkt belong to "Virtual Machine Platforms & Containers" category of the tech stack.
Some of the features offered by Docker are:
- Integrated developer tools
- open, portable images
- shareable, reusable apps
On the other hand, rkt provides the following key features:
- Composable. All tools for downloading, installing, and running containers should be well integrated, but independent and composable.
- Security. Isolation should be pluggable, and the crypto primitives for strong trust, image auditing and application identity should exist from day one.
- Image distribution. Discovery of container images should be simple and facilitate a federated namespace, and distributed retrieval. This opens the possibility of alternative protocols, such as BitTorrent, and deployments to private environments without the requirement of a registry.
"Rapid integration and build up" is the primary reason why developers consider Docker over the competitors, whereas "Security" was stated as the key factor in picking rkt.
Docker and rkt are both open source tools. It seems that Docker with 53.8K GitHub stars and 15.5K forks on GitHub has more adoption than rkt with 8.68K GitHub stars and 829 GitHub forks.
lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.
Pros of Docker
- Rapid integration and build up824
- Isolation692
- Open source521
- Testability and reproducibility505
- Lightweight460
- Standardization218
- Scalable185
- Upgrading / downgrading / application versions106
- Security88
- Private paas environments85
- Portability34
- Limit resource usage26
- Game changer17
- I love the way docker has changed virtualization16
- Fast14
- Concurrency12
- Docker's Compose tools8
- Easy setup6
- Fast and Portable6
- Because its fun5
- Makes shipping to production very simple4
- Highly useful3
- It's dope3
- Its cool2
- MacOS support FAKE2
- Simplicity, isolation, resource effective2
- Open source and highly configurable2
- Does a nice job hogging memory2
- Package the environment with the application2
- Very easy to setup integrate and build2
- HIgh Throughput2
- Docker hub for the FTW2
- Super2
- Asdfd0
Pros of rkt
- Security5
- Robust container portability3
- Composable containers2
Sign up to add or upvote prosMake informed product decisions
Cons of Docker
- New versions == broken features8
- Unreliable networking6
- Documentation not always in sync6
- Moves quickly4
- Not Secure3
Cons of rkt
Sign up to add or upvote consMake informed product decisions
What is Docker?
What is rkt?
Need advice about which tool to choose?Ask the StackShare community!
What companies use rkt?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Docker?
What tools integrate with rkt?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+9
+7+14
+17
+32
+8
+8+17