W. Trevor King

On Fri, Jan 22, 2016 at 12:22:17PM -0800, Doug Davis wrote: > I'm distinguishing between `runc stop ` and `runc kill ` If you have the latter (which I prefer),...

On Fri, Jan 22, 2016 at 01:40:54PM -0800, Abin Shahab wrote: > What is the state of the system after a kill/stop with SIGTERM? I > imagine the init process...

On Mon, Jan 25, 2016 at 06:24:39AM -0800, Doug Davis wrote: > See https://github.com/opencontainers/runc/pull/506 For a more compact reference, see [1](http://karelzak.blogspot.com/2015/04/persistent-namespaces.html) and references to bind mounting in “The /proc/[pid]/ns/ directory”...

On Fri, Oct 28, 2016 at 10:13:12AM -0700, Rich Moyse wrote: > … is there an effort to more directly represent this notion of > lineage into this image spec…...

I think the idea was to avoid failing a runtime as non-compliant if the host system didn't support a feature. But with the current wording, you can have compliant runtimes...

Previous discussion in the context of Linux capability strings [here][1] and in #755. [1]: https://github.com/opencontainers/runtime-spec/pull/673#discussion_r99353136

On Wed, Apr 13, 2016 at 11:01:25PM -0700, Brandon Philips wrote: > 1 Detached signature sitting alongside each CAS object (this is the > approach appc takes) This sounds like...

On Wed, Apr 20, 2016 at 08:15:37PM -0700, Kamal Marhubi wrote: “… they use Canonical JSON to form the byte sequence to be signed based on the `signed` object.” That...

On Tue, May 24, 2016 at 02:12:32PM -0700, Vincent Batts wrote: > It does make me think, once examples like this bubble up and folks > have options to choose...

On Wed, Jun 08, 2016 at 04:39:59PM -0700, Brandon Philips wrote: > I meant to move this to post-v1.0.0 as no one has stepped up and as > it is...