Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
The Open Container Initiative (OCI) serves as an open governance framework aimed at developing industry-wide standards for container formats and runtimes. Launched on June 22, 2015, by Docker alongside other prominent figures in the container sector, the OCI encompasses two main specifications: the runtime specification (runtime-spec) and the image specification (image-spec). The runtime specification delineates the process for executing a "filesystem bundle" that has been extracted onto a disk. In practice, an OCI implementation would download an OCI Image, subsequently unpacking it into a corresponding OCI Runtime filesystem bundle. Following this, the OCI Runtime is responsible for executing the OCI Runtime Bundle. Additionally, the OCI operates as a lightweight governance project under the Linux Foundation, promoting transparency and collaboration within the container ecosystem. Its establishment marked a significant step forward towards unifying diverse container technologies and ensuring interoperability across platforms.
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
No
API Access
Has API
No
Integrations
Docker
Yes
Alibaba CloudAP
Yes
D2iQ
Yes
Dell EMC Avamar
Yes
Facebook
Yes
Fedora CoreOS
Yes
Fujitsu Biometrics-as-a-Service
Yes
Google Cloud Platform
Yes
Huawei APM
Yes
IBM Cloud
Yes
Integrations
Docker
Yes
Alibaba CloudAP
No
D2iQ
No
Dell EMC Avamar
No
Facebook
No
Fedora CoreOS
No
Fujitsu Biometrics-as-a-Service
No
Google Cloud Platform
No
Huawei APM
No
IBM Cloud
No
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Deployment
Web-Based
No
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
Yes
Chromebook
No
Deployment
Web-Based
No
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
Yes
Chromebook
No
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Vendor Details
Company Name
Open Container Initiative (OCI)
Website
opencontainers.org
Vendor Details
Company Name
Open Container Initiative (OCI)
Website
github.com/opencontainers/runc