What users are saying about
2 Ratings
196 Ratings
2 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7 out of 100
196 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.1 out of 100

Likelihood to Recommend

CoreOS rkt

CoreOS rkt is well suited for any development environment where operating systems and hardware are not homogeneous. CoreOS rkt allows us to write code on one machine with the confidence that it will work on any other. This has been immensely helpful as our developers are often switching to the latest and greatest machines and operating systems. CoreOS rkt is less suited for environments that are not Software as a Service. There is often no need to bring the entire developer environment and associated dependencies when delivering a one time product. In these environments CoreOS rkt just adds unneeded overhead.
Anonymous | TrustRadius Reviewer

Docker

Docker is great for when you would want to use a VM for any given application, but don't need the overhead of the whole OS. Docker containers use very little computing resources, boot up very quickly, and are very easy to set up. An instance where Docker may not be appropriate would be for an application that requires good security. If in this situation, a true VM would probably be your best bet.
Anonymous | TrustRadius Reviewer

Pros

CoreOS rkt

  • Running a secure container without messing up with low-level details
  • Very clear and straightforward approach to building a container
  • A way to go for new projects thinking of containers
  • Comprehensive and well-written documentation compatible with UNIX keep it simple way of thinking
Ján Sáreník | TrustRadius Reviewer

Docker

  • Containerization - allowing multiple micro-services to function together without in-depth orchestration at the VM level.
  • Rapid deployment - a developer with appropriate access can simply push to the correct remote and the deploy happens automatically from there
  • Decouples provisioning from VM administration - allows containers to be deployed (more) regardless of VM set up.
Ben Lachman | TrustRadius Reviewer

Cons

CoreOS rkt

  • Market share, it's often very difficult to find new talent who use CoreOS rkt.
  • Lack of wow features, CoreOS rkt doesn't necessarily offer any immediate advantages over other container solutions.
Anonymous | TrustRadius Reviewer

Docker

  • As a NON-heavy user, definitely it's a bit intimidating in the onboarding phase. It's hard to understand what everything is for and how to use it appropriately. As I wrote before, this could be because I'm not a hard developer myself.
  • At least on Windows 10, I always have problems turning it on. It has problems starting, I need to quit/start again, and then it works. I'm supposed to have a stable version, not sure if it's only myself.
Anonymous | TrustRadius Reviewer

Usability

CoreOS rkt

No score
No answers yet
No answers on this topic

Docker

Docker 8.0
Based on 1 answer
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
Anonymous | TrustRadius Reviewer

Support Rating

CoreOS rkt

No score
No answers yet
No answers on this topic

Docker

Docker 10.0
Based on 2 answers
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
Anonymous | TrustRadius Reviewer

Alternatives Considered

CoreOS rkt

Docker, lxc, Ubuntu Snappy, partisan chroot+unshareReformulating the problem and realizing a container is not necessary when a testing environment with clearly defined behavior.
Ján Sáreník | TrustRadius Reviewer

Docker

Prior to docker, we had a custom build and deployment system. For local development, we use VirtualBox to host our VMs, while our custom VMs resided directly on the servers. We chose Docker primarily to allow us to get rid of our custom deployment system, both simplifying build and deploy processes and reducing the support needs of our own custom solution.
Anonymous | TrustRadius Reviewer

Return on Investment

CoreOS rkt

  • Developers spend less time configuring and more time coding.
  • Less time training developers as CoreOS rkt lets them use whatever hardware and operating system they want.
  • Reduced our IT costs, solutions are containerized using CoreOS rkt meaning they can write one solution with many developers in mind.
Anonymous | TrustRadius Reviewer

Docker

  • Docker has made it easy to refactor applications and isolate performance bottlenecks so that those aspects can be scaled independently. This has improved our overall application performance.
  • Docker has shortened our release cycle by enabling us to automate more of our testing/deployment pipeline. As a result, we are able to push new releases and bug-fixes more frequently.
  • Docker has reduced the incidence of bugs that only manifest in our production environment because developers are able to test locally with an identical configuration.
Brian Dentino | TrustRadius Reviewer

Pricing Details

CoreOS rkt

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Docker

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison