Skip to main content
CoreOS rkt / Container Linux (project ended)

CoreOS rkt / Container Linux (project ended)


What is CoreOS rkt / Container Linux (project ended)?

CoreOS rkt or Container Linux was a rival to Docker that was acquired by Red Hat, then given to the Cloud Native Computing Foundation (CNCF). The project has since been discontinued.

Read more
Recent Reviews
Read all reviews
Return to navigation


View all pricing

What is CoreOS rkt / Container Linux (project ended)?

CoreOS rkt or Container Linux was a rival to Docker that was acquired by Red Hat, then given to the Cloud Native Computing Foundation (CNCF). The project has since been discontinued.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

1 person also want pricing

Alternatives Pricing

What is Red Hat OpenShift?

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

What is GitLab?

GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps…

Return to navigation

Product Details

What is CoreOS rkt / Container Linux (project ended)?

CoreOS rkt / Container Linux (project ended) Video

Demo Introduction to ContainerOS

CoreOS rkt / Container Linux (project ended) Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings



(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
We use CoreOS rkt in as developers and as an organization. My department uses CoreOS rkt to compartmentalize all of our developer operation tools and to keep systems homogeneous across hardware. My organization as a whole use CoreOS rkt to containerize and scale customer instances.

As a developer CoreOS rkt is a lifesaver, it has allowed us to write tools focused on developer productivity and use them across the department regardless of underlying operating system. We have hundreds of compilers, linters, and unit tests across dozens of languages stored in CoreOS rkt.

As an organization we use CoreOS rkt when spinning up new customers. This has been advantageous because we can run multiple customers from one VPC. It also means we can scale up a customers environment almost instantaneously. We often have customers who's resource needs change on a daily basis, CoreOS rkt has allowed us to scale with our customers.
  • Containerization, CoreOS rkt is particularly well suited when running multiple processes on one server.
  • Simplicity, CoreOS rkt is easy and quick to get up and running.
  • Speed, CoreOS rkt takes few resources and performs with little overhead.
  • The API, gRPC is a wonderfully easy framework to use.
  • 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.
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.
  • 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.
  • Docker
We evaluated CoreOS rkt and Docker when selecting software solutions for my department. We ended up using CoreOS rkt because of how well it fits with CoreOS and the choice of gRPC for the API. We provide a managed service that runs CoreOS on a bare metal server, CoreOS rkt was a logical choice for compatibility. We also found that developers were having better scusess interacting with gRPC than other container engines REST protocols. It was a close race but eventually there were just enough small benefits to push CoreOS rkt in front of the competition.
March 10, 2017

Keep It Simple - RKT

Ján Sáreník | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
We were looking at rkt as a way to automate Linux containers on ARM. It is not currently being used and even back then it was turned down. On the other hand there were also positives to rkt compared to docker where rkt focuses on what it is doing and is not a whole new packaging world with a distribution mechanism etc.
  • 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
It is very well suited for local testing where one knows what is being worked on and knows all the dependencies of the software project. On the other hand, it would be less appropriate in situations where a simple chroot can do the trick without the overhead of running a Go application.
  • It helps with providing a stable environment which does not require reinventing the wheel
  • Docker, Ubuntu and Snappy
Docker, lxc, Ubuntu Snappy, partisan chroot+unshare

Reformulating the problem and realizing a container is not necessary when a testing environment with clearly defined behavior.
Heroku, OpenVZ, Docker
Return to navigation