The Containers Working Group
This working group is organized to discuss the needs of the HPC community, and how they can be integrated into existing or new Open Container Initiative (OCI) projects. You can browse ideas here, and contribute to them directly at the repository. In this site you will find:
- ideas: What ideas do we have for updating or extending OCI?
- discussion: Each idea is linked to a discussion thread.
- review: of existing specs and the issues they have in an HPC context.
- share: your current HPC projects and how OCI works (or does not work) for you.
Please see the repository for details on how to contribute.
Finished
- To start with an effort to improve the overall interface to read OCI documentation, (this issue) we created the rfc-jekyll template, and it is now deployed at specs.opencontainers.org so the OCI specs are easier to read.
In Progress
- Discussion of a survey is underway! The survey (and IRB papers) were ready in early September, but moving forward was stopped by working group members that have not followed up yet.
- To tackle clarification of dealing with symbolic and hardlinks in the image spec we’ve opened an issue for discussion and started working on an update to the image-spec to address it.
Please feel free to jump in to provide feedback or help with these efforts!
Content
- Ideas: for how we can contribute a spec or project.
- OCI Specs and Projects: review (and comments) on current OCI specs and projects.
- HPC projects: notes about why OCI works (or not) for our projects.
- Contributing: instructions are in the repository README.
Ideas
The following ideas are under development!
- A Building Service
- Batch Orchestration
- Binary diff layers
- Clarify symlink and hardlink rules
- Conformance tests
- Container Metadata
- Containers Technologies for HPC Survey
- Containers Working Group for HPC Survey
- Content-Length: required
- Digest input clarification
- Dockerfile specification
- Dynamic Manifests
- ENTRYPOINT and CMD are too complex
- Fully unprivileged runtime support
- Honor media-type Accepts:
- Layer Annotation
- Monolithic Image Layer
- More examples in spec
- POST blob upload required
- Pushing Arbitrary Blobs
- Single-ID images
- Stateless runtime support
- Tar flavor
- Whiteouts out-of-band