Docker vs ZeroVM vs rkt | What are the differences? | StackShare

Docker vs ZeroVM vs rkt

Overview

Docker

Stacks179.0K

Followers143.8K

Votes3.9K

ZeroVM

Stacks2

Followers10

Votes0

GitHub Stars826

Forks77

rkt

Stacks29

Followers112

Votes10

🔥 Trending in Container Registry on StackShare

SpinKube Container Registry

Hyper-efficient serverless on Kubernetes, powered by WebAssembly

Try it View Docs Alternatives

Try

Advice on Docker, ZeroVM, rkt

Florian

IT DevOp at Agitos GmbH

Oct 22, 2019

Decided

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.

482k views482k

Comments

Detailed Comparison

Docker	ZeroVM	rkt
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	ZeroVM is an open source virtualization technology that is based on the Chromium Native Client (NaCl) project. ZeroVM creates a secure and isolated execution environment which can run a single thread or application. ZeroVM is designed to be lightweight, portable, and can easily be embedded inside of existing storage systems.	Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.
Integrated developer tools; open, portable images; shareable, reusable apps; framework-aware builds; standardized templates; multi-environment support; remote registry management; simple setup for Docker and Kubernetes; certified Kubernetes; application templates; enterprise controls; secure software supply chain; industry-leading container runtime; image scanning; access controls; image signing; caching and mirroring; image lifecycle; policy-based image promotion	Small, Light, Fast - ZeroVM is extremely small, lightweight, and fast. An execution environment can start in as little as 5 milliseconds.;Secure - ZeroVM security is derived from the Chromium Native Client (NaCl) project and is based on the concept of software fault isolation.;Hyper-Scalable - ZeroVM makes it easy to create large clusters of instances, aggregating the compute power of many individual physical servers into a single execution environment.;Embeddable - ZeroVM is designed to be embedded into existing storage systems.;Functional (Deterministic) - Execution inside a ZeroVM environment is functionally pure or deterministic, meaning that for any given set of inputs ZeroVM will always produce the exact same output.	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.;Open. The format and runtime should be well-specified and developed by a community. We want independent implementations of tools to be able to run the same container consistently.
Statistics
GitHub Stars -	GitHub Stars 826	GitHub Stars -
GitHub Forks -	GitHub Forks 77	GitHub Forks -
Stacks 179.0K	Stacks 2	Stacks 29
Followers 143.8K	Followers 10	Followers 112
Votes 3.9K	Votes 0	Votes 10
Pros & Cons
Pros 823 Rapid integration and build up 692 Isolation 521 Open source 505 Testability and reproducibility 460 Lightweight Cons 8 New versions == broken features 6 Unreliable networking 6 Documentation not always in sync 4 Moves quickly 3 Not Secure	No community feedback yet	Pros 5 Security 3 Robust container portability 2 Composable containers
Integrations
Java Docker Compose VirtualBox Linux Amazon EC2 Container Service Docker Swarm boot2docker Kubernetes Docker Machine Vagrant	No integrations available	No integrations available

What are some alternatives to Docker, ZeroVM, rkt?

LXD

LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new, better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding to create and manage the containers. It's basically an alternative to LXC's tools and distribution template system with the added features that come from being controllable over the network.

LXC

LXC is a userspace interface for the Linux kernel containment features. Through a powerful API and simple tools, it lets Linux users easily create and manage system or application containers.

Vagrant Cloud

Vagrant Cloud pairs with Vagrant to enable access, insight and collaboration across teams, as well as to bring exposure to community contributions and development environments.

Studio 3T

It's the only MongoDB tool that provides three ways to explore data alongside powerful features like query autocompletion, polyglot code generation, a stage-by-stage aggregation query builder, import and export, SQL query support and more.

OpenVZ

Virtuozzo leverages OpenVZ as its core of a virtualization solution offered by Virtuozzo company. Virtuozzo is optimized for hosters and offers hypervisor (VMs in addition to containers), distributed cloud storage, dedicated support, management tools, and easy installation.

SmartOS

It combines the capabilities you get from a lightweight container OS, optimized to deliver containers, with the robust security, networking and storage capabilities you’ve come to expect and depend on from a hardware hypervisor.

Clear Containers

We set out to build Clear Containers by leveraging the isolation of virtual-machine technology along with the deployment benefits of containers. As part of this, we let go of the "generic PC hardware" notion traditionally associated with virtual machines; we're not going to pretend to be a standard PC that is compatible with just about any OS on the planet.

Flatpak

It is a next-generation technology for building and distributing desktop applications on Linux

Lima

It launches Linux virtual machines with automatic file sharing, port forwarding, and containerd. It can be considered as some sort of unofficial "macOS subsystem for Linux", or "containerd for Mac". It is expected to be used on macOS hosts, but can be used on Linux hosts as well. It may work on NetBSD and Windows hosts as well.