Vincent Batts

@stevvooe related to https://github.com/opencontainers/image-spec/issues/600 ?

@AkihiroSuda the discussion looks good and healthy. And it looks like implementations are iterating to find consensus and polish out issues found. I haven't seen any feedback that should stop...

fair. It does make me think, once examples like this bubble up and folks have options to choose from, there may need to be additional media-types/MIME-types for signature objects.

Per the face-2-face at LinuxCon.EU, it was generally agreed that the spec ought to at least mention the points that are _signable_, even if not declaring a method to do...

it seems to me, this could be done with the discussed "references API"

cc @opencontainers/certification-maintainers

@RobDolinMS perhaps so

The conformance issue was closed because it went stale. I still think a conformance/validation piece would be nice here.

As a nit, I did not recommend embedding the document, but rather brainstorming possibilities. On Wed, Jun 8, 2016, 13:32 W. Trevor King [email protected] wrote: > On Wed, Jun 08,...

It seems like a generally useful check. Liveness is just that the pid is up, but a health check could be applied across most container runtime use-cases.