The Open Container Initiative (OCI) is an open governance project that defines standardized specifications for container runtime formats and container image formats.
The Open Container Initiative (OCI) is a Linux Foundation governance structure established by Docker, Red Hat, Google, and Microsoft in 2015 to create open industry standards for container runtimes and image formats. The OCI specifications ensure that container images built by Docker, Podman, Buildah, or Kaniko run seamlessly across any compliant runtime engine (containerd, CRI-O, runc).
Lint container build instructions using the Dockerfile Linter or migrate container definitions with Docker Compose to K8s.
| Specification | Purpose | Reference Implementations |
|---|---|---|
| Image Specification (image-spec) | Defines container tarball layers, manifests, configuration JSON, and index descriptors | Docker Image v2, Podman Images |
| Runtime Specification (runtime-spec) | Defines container execution lifecycle, Linux cgroups, namespaces, and security profiles | runc, crun, youki |
| Distribution Specification (distribution-spec) | Defines HTTP API protocols for pushing and pulling container images to/from registries | GitHub Packages, Docker Hub, AWS ECR |
Free, browser-based utilities to test, generate, and inspect Open Container Initiative (OCI) Specifications payloads directly.
Lint, validate, format, and optimize Dockerfiles with Hadolint-compatible rules, security checks, and multi-stage analysis.
Convert docker-compose.yml to Kubernetes Deployment, Service, ConfigMap, and PVC manifests.
Validate, lint, and format Kubernetes manifests against structure rules, deprecated APIs, and security best practices.
