rkt

An App Container runtime that integrates with init systems, is compatible with other container formats like Docker, and supports alternative execution engines like KVM.

Programming language: Go

Tags: Software Packages     Other Software    

Latest version: v1.30.0

README

:warning: End of project :warning:

This project has ended, and all development/maintenance activities have halted.

As it is free software, people are free and welcome to fork and develop the codebase on their own. However, to avoid any confusion, the original repository is archived and we recommend any further fork/development to proceed with an explicit rename and rebranding first.

We encourage all interested parties to mirror any relevant bits as we can't actively guarantee their existence in the future.

---

rkt - the pod-native container engine

[rkt Logo](logos/rkt-horizontal-color.png)

rkt (pronounced like a "rocket") is a CLI for running application containers on Linux. rkt is designed to be secure, composable, and standards-based.

Some of rkt's key features and goals include:

• Pod-native: rkt's basic unit of execution is a pod, linking together resources and user applications in a self-contained environment.
• Security: rkt is developed with a principle of "secure-by-default", and includes a number of important security features like support for [SELinux][selinux], [TPM measurement][tpm], and running app containers in [hardware-isolated VMs][kvm].
• Composability: rkt is designed for first-class integration with init systems (like [systemd][systemd], upstart) and cluster orchestration tools (like [Kubernetes][kubernetes] and [Nomad][nomad]), and supports [swappable execution engines][architecture].
• Open standards and compatibility: rkt implements the [appc specification][rkt-and-appc], supports the Container Networking Interface specification, and can run [Docker images][docker] and OCI images. Broader native support for OCI images and runtimes is in development.

Project status

The rkt v1.x series provides command line user interface and on-disk data structures stability for external development. Any major changes to those primary areas will be clearly communicated, and a formal deprecation process conducted for any retired features.

Check out the [roadmap](ROADMAP.md) for more details on the future of rkt.

Trying out rkt

To get started quickly using rkt for the first time, start with the ["trying out rkt" document](Documentation/trying-out-rkt.md). Also check [rkt support on your Linux distribution](Documentation/distributions.md). For an end-to-end example of building an application from scratch and running it with rkt, check out the [getting started guide](Documentation/getting-started-guide.md).

Getting help with rkt

There are a number of different avenues for seeking help and communicating with the rkt community:

• For bugs and feature requests (including documentation!), file an issue
• For general discussion about both using and developing rkt, join the rkt-dev mailing list
• For real-time discussion, join us on IRC: #[rkt-dev][irc] on freenode.org
• For more details on rkt development plans, check out the GitHub milestones

Most discussion about rkt development happens on GitHub via issues and pull requests. The rkt developers also host a semi-regular community sync meeting open to the public. This sync usually features demos, updates on the roadmap, and time for anyone from the community to ask questions of the developers or share users stories with others. For more details, including how to join and recordings of previous syncs, see the sync doc on Google Docs.

Contributing to rkt

rkt is an open source project and contributions are gladly welcomed! See the [Hacking Guide](Documentation/hacking.md) for more information on how to build and work on rkt. See [CONTRIBUTING](CONTRIBUTING.md) for details on submitting patches and the contribution workflow.

Licensing

Unless otherwise noted, all code in the rkt repository is licensed under the [Apache 2.0 license](LICENSE). Some portions of the codebase are derived from other projects under different licenses; the appropriate information can be found in the header of those source files, as applicable.

Security disclosure

If you suspect you have found a security vulnerability in rkt, please do not file a GitHub issue, but instead email [email protected] with the full details, including steps to reproduce the issue. CoreOS is currently the primary sponsor of rkt development, and all reports are thoroughly investigated by CoreOS engineers. For more information, see the CoreOS security disclosure page.

Known issues

Check the [troubleshooting document](Documentation/troubleshooting.md).

Related Links

Integrations and Production Users

• Projects integrating with rkt
• Production users