MeetingMinutes: 2015 09 16

Home ▸ MeetingMinutes:

Discussion w/ Video:

Video at https://bluejeans.com/1771332256/

Topics:

• The maintainers want to discuss the usability of the current spec and discuss issues/improvements in usability. Allowing specifying user/group by name, Simplifying specifying some options
• Discuss the next steps for the spec.
  • bundle and hashing(identity)
  • A unified model between container and VM?
• Carried Over:
  • “Misc” tools, like OCT
    • https://github.com/huawei-openlab/oct/blob/master/README.md (David Liang)
  • opencontainers/specs docs cleanup/formatting (vbatts)

Attendees:

• Alexander Morozov
• Brandon Philips
• Doug Davis
• jojy
• Julz Friedman
• Lai Jiangshan
• Michael Crosby
• Mrunal Patel
• Phil Estes
• Stefan Saru
• Trevor King
• Vincent Batts
• Vishnu Kannan

Minutes:

• user/group by name
  • https://github.com/opencontainers/specs/pull/191
  • We could support user name or uid/gid. If both are specified, then we error out.
  • We need to still support additional groups
    • sharing volumes between different containers
    • quota based filesystems can use gids
• Introduce separate volumes concept for bind mounts?
  • Could help with portability
  • Implement quotas per volume
  • Vishnu/Michael to list use cases
• Simpler config
  • Might not make sense in the config as there are too many options
  • Mrunal/Michael will make notes
  • Possibly separate out process.json to keep the separation of concerns clearer. Reused when creating a container that’s the same with a different process running in itwith funC exec …. Mrunal doesn’t care, but is concerned about the number of config files; Julz wants to separate them to have smaller, simpler files.
    • use-case is to create a second bundle that is similar but with a different process, without having to edit JSON.
    • Additional use case is funC exec-style. Julz to document this use case, but it’s close to ‘docker exec …’. Brandon’s not convinced that ‘docker exec …’ is a great example.
    • Another use-case is to create a second bundle that is similar but with a different process, without having to edit JSON.
• Status
  • How do we know when the process is up? poll/inotify for state.json
  • ‘funC start --daemon …’ to return after the container is up (after launching the usual stuff in a daemon process)
  • Julz to write up his use case for further discussion
• Next steps: Verifying bundle identity (Brandon to summarize and create an issue)
• Validation tool (Mrunal to work on it)
• Generation tool should probably provide a minimal config
  • https://github.com/mrunalp/ocitools
• Runtime-specific information in state.json
  • https://github.com/opencontainers/specs/pull/188
  • Brandon’s concerned about common operations across implementations (e.g. can’t exec in a hypervisor container). Vishnu agrees about making exec optional, provide enough to express it where possible.
  • runv exec is in the hyper team’s todo list.
  • We’d like to connect with the runV folks on this, but didn’t have any on the call. And also Windows containers, but we didn’t have any of them on the call either.
• Any OCT people on the call? No.

Next Meeting:

• ACTION(vishnu/crosby): list out some use cases for volumes separate from bind mounts