G2 Crowd builds the world's largest business commerce platform fueled by $100M in funding ­čÜÇ

rkt

4.1
(6)

rkt is an open source container runtime designed for composability, security, and speed.

Work for rkt?

Learning about rkt?

We can help you find the solution that fits you best.

rkt Reviews

Ask rkt a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 6 rkt reviews
LinkedIn Connections
rkt review by Manil C.
Manil C.
Validated Reviewer
Verified Current User
Review Source

"Rocket is a project to definitely watch"

What do you like best?

Rocket (rkt) is a container runtime engine, unlike Docker (the main container technology today), it is build from the ground up with security in mind. Its is also integrated with linux security standards like SELinux. For instance, it allows you to sign images and check the integrity of images before running them. It also build around the unix binary standard and thus it can easily integrated with init systems (e.g. systemd).

What do you dislike?

It still lack a lot of features that make it easily start using it. For instance, unlike docker it doesn't have a GUI and runs only on Unix-like systems (no runtime for Windows or OS X). It's stil a young project that's not very mature and it lacks integrations with tools in the container ecosystem (e.g. kubernetes).

Recommendations to others considering the product

Rocket is a project to watch closely, it is in ints early stage but seems promising as the company (i.e. CoreOS) behind is putting a lot of efforts.

What business problems are you solving with the product? What benefits have you realized?

I looked for rkt when I was looking for a containerasation solution, I find it a good solution but as it was not very mature (especially it's integration with other toolings) I've end up not choosing it.

Sign in to G2 Crowd to see what your connections have to say about rkt
rkt review by Karl H.
Karl H.
Validated Reviewer
Verified Current User
Review Source

"Solid technical foundation and clean interface but not ready yet"

What do you like best?

The simple design of the runtime as compared to docker. The ability to easily resource control and integrate with the host operating system (through systemd), which is a consequence of the simple runtime design. The ability to use systemd-nspawn and ease of using a proper PID 1 in the container (as opposed to docker). The pod containing multiple containers is a rather nice feature too. Finally ACI a rather well defined specification of how to containerize an image.

What do you dislike?

It is not ready for production use yet. The documentation is incomplete and some design decisions are yet to be made. The lack of ready made containers conforming to ACI, though that is mitigated by the docker to aci converter but canonical examples would be nice.

Generally the fact that it feels very much not done is the problem. There are also some bugs blocking full production use at the moment of writing, but improvements are happening fast.

Recommendations to others considering the product

Try it out but keep it the lab until it is ready (pretty much the project recommendation also). The design is really nice though so read up on, you might even learn some about the design of docker.

What business problems are you solving with the product? What benefits have you realized?

Primarily app centric containers (as opposed to light weight virtual machines). rkt fits better into our modular software (smaller self contained units constallations of units) than docker. I would stick with docker for containerizing a postgres-, maria- or mySQL database probably, but a compute centric app with clearly defined runtimes and boundaries fits well into rkt.

What Container Engine solution do you use?

Thanks for letting us know!
rkt review by Ján S.
Ján S.
Validated Reviewer
Verified Current User
Review Source

"Wonderful environment"

What do you like best?

I've used Rocket when I was learning

Gregor Kiczales's course on Systematic Program Design. Rocket provided a very clean interface to understand important principles like designing functions by writing tests first.

What do you dislike?

I do not like that Rocket is not used more because this way there is not enough opportunity for me to use it on daily basis.

Recommendations to others considering the product

Try the free online course on Systematic Program Design.

What business problems are you solving with the product? What benefits have you realized?

I usually solve automation problems and there's a lot from the Rocket way of thinking that I can reuse in any environment.

rkt review by Administrator in Telecommunications
Administrator in Telecommunications
Validated Reviewer
Verified Current User
Review Source

"A containerosp sulotion build with container like rkt or Docker"

What do you like best?

1. The CLI interface is simple and no daemon.

2. The code is more clear architecture than Docker.

3. It's easy integrate with existing system and environment.

What do you dislike?

1. No ACI format service.

2. No push function.

Recommendations to others considering the product

1. Support the P2P function.

2. Lunch a image service supported rkt.

3. More documents.

4. More community events and conferences about it.

5. More open community for developers and company.

6. More business case using rkt.

7. More run environments in cloud.

What business problems are you solving with the product? What benefits have you realized?

Provide a new solution of DevOps base container, it's a new DevOps concept.

rkt review by Vaibhav K.
Vaibhav K.
Validated Reviewer
Verified Current User
Review Source

"Rocket Linux Container Orchestration Tool Review"

What do you like best?

- The ACI specification

- No daemon - this makes it less vulnerable and easy to add functionality

- Deduplicated images

What do you dislike?

- Use of systemd-nspawn: this makes it incompatible with other platforms

- Documentation talking about stages etc i.e. the details

What business problems are you solving with the product? What benefits have you realized?

I am researcher at a multi national company.

rkt review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"I use it in production"

What do you like best?

It don't have a daemon like docker daemon. Specification made by community.

What do you dislike?

Integration with kubernets it is not completed

What business problems are you solving with the product? What benefits have you realized?

All our micro-services run in a rkt.

We don't need a docker registry.

Kate from G2 Crowd

Learning about rkt?

I can help.
* We monitor all rkt reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.