Standard container specification
A core result of the OCI effort is the creation and development of the overarching container specification. The specification has five core principles that all containers should follow, which I will briefly paraphrase:
- The container must have standard operations to create, start, and stop containers across all implementations.
- The container must be content-agnostic, which means that type of application inside the container does not alter the standard operations or publishing of the container itself.
- The container must be infrastructure-agnostic as well. Portability is paramount; therefore, the container must be able to operate just as easily in GCE as in your company's data center or on a developer's laptop.
- A container must also be designed for automation, which allows us to automate across the build, as well as for updates and the deployment pipelines. While this rule is a bit vague, the container implementation should not require onerous manual steps for creation...
