Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Mirantis Container Runtime (MCR), which was previously known as Docker Engine Enterprise, serves as a secure and robust container runtime designed for enterprise use, allowing development teams to create and manage containers on both Linux and Windows platforms while utilizing the familiar Docker CLI, Dockerfiles, and APIs essential for mission-critical applications. This solution is fully aligned with Docker-centric workflows and toolchains, ensuring a smooth transition from development to production with rigorously tested and validated releases across various operating systems, accompanied by comprehensive CVE patching and bug fixes that maintain workload reliability. Furthermore, MCR emphasizes top-tier security through FIPS 140-2 certified cryptographic modules, implements mandatory access controls such as AppArmor and SELinux, and incorporates image signature verification, alongside support for sandboxed runtimes like Kata and gVisor, all aimed at maintaining trusted and compliant containers. The combination of these features positions MCR as a leading choice for organizations seeking to enhance their container management capabilities while adhering to strict security standards.
Description
runc is a command-line interface utility designed to create and manage containers in accordance with the OCI specification, but it is limited to Linux environments. For compilation, it requires Go version 1.17 or higher, and to activate seccomp features, libseccomp must be installed on your system. The tool offers optional build tags that allow for the inclusion of various functionalities, many of which are activated by default. Currently, runc allows its test suite to be executed through Docker, and simply typing `make test` initiates this process. Although there are additional make targets available for testing outside of a container, this practice is discouraged since the tests assume permission to read and write files freely. You can also specify individual test cases using the TESTFLAGS variable, or focus on a particular integration test with the TESTPATH variable; for rootless integration tests, the ROOTLESS_TESTPATH variable should be used. It’s important to remember that runc serves as a foundational tool rather than one intended for end-user interaction, making it more suitable for developers who need lower-level container management capabilities. Ultimately, understanding its purpose and use cases is essential for effective application.
API Access
Has API
API Access
Has API
Integrations
Docker
AppArmor
Kubernetes
Mirantis Secure Registry
OpenTelemetry
Swarm
Integrations
Docker
AppArmor
Kubernetes
Mirantis Secure Registry
OpenTelemetry
Swarm
Pricing Details
No price information available.
Free Trial
Free Version
Pricing Details
No price information available.
Free Trial
Free Version
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Vendor Details
Company Name
Mirantis
Founded
1999
Country
United States
Website
www.mirantis.com
Vendor Details
Company Name
Open Container Initiative (OCI)
Website
github.com/opencontainers/runc