-
Notifications
You must be signed in to change notification settings - Fork 549
MeetingMinutes: 2015 08 12
Vincent Batts edited this page Sep 4, 2015
·
3 revisions
- https://github.com/opencontainers/specs/pull/88
- Devices/cgroups integration
- ExtraFiles https://github.com/opencontainers/specs/pull/100
- application specific metadata (versions of libraries/commands)
- testing - https://github.com/huawei-openlab/oct
- https://github.com/opencontainers/specs/issues/95
- Video
- Mrunal Patel
- Vincent Batts
- Rohit Jnagal
- Brandon Philips
- IRC
- Phil Estes
- Lily Chen
- W. Trevor King
- Rob Dolin
- David Liang
-
https://github.com/opencontainers/specs/issues/108
- application and dependency metadata (to be able to apply version restrictions of version (openssl > x.x.x))
- bundled application may not even be aware of lower level components
- an optional field or structure
- no one is in disagreement that label/annotation is needed/useful
- we’ll iron out details of this on the mailing list thread
- https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/p_u2xps6jvo
- concept of runtime.json
- https://github.com/opencontainers/specs/pull/88
- container to specify UID? for chown’d rootfs, this is a benefit
- the container specifying minimum resource requirements is not entirely useful, and would provide inflexibility. You’ll find out quickly when the application falls over with ENOMEM.
- Namespaces, there are times to need to run in the host namespace or another namespace. But this is up to the runner of the image to specify, not the container to dictate.
- philips to add language about UID mapping
- Devices/cgroups integration
- deferred for alexander’s participation
- ExtraFiles https://github.com/opencontainers/specs/pull/100
- what the runtime would provide, how would it handle the file descriptors and pass down to the child
- mrunal to update PR (or have another PR) and provide how external files can be use (like ssh or socket activation)
- testing
- like https://github.com/huawei-openlab/oct
- tools repo to validate spec
- start with
runtime.json
validator - then a minimal init for inside the container to validate the environment
- OCT is largely for orchestration and frameworks.
- We’ll invite someone to speak on this next week
- mrunal to start a tracker story for config and env validation, that we all can chip in on.
- Initial Draft of spec
- OpenContiners.org lists "July" (not since opencontainers/web@b9f0a511)
- requirements on nailing down this kind of announcement, like the validation topic
- brandon to file issue on releasing, version number, and tooling to validate
•
Be sure to read the CONTRIBUTING guidelines before reporting a new issue or opening a new pull request.