leigh capili

Also, we may be able to improve this failure mode. It's a bit unfortunate that pulling concurrent images creates an ambiguous store that breaks even all future non-concurrrent runs. Maybe...

We have merged #656 which reduces the burden on PR's and moves to a weekly periodic check on master. We should still follow this up with PR checks for links...

From what I remember working on this -- the write logic should inspect the parent cgroup to understand the hierarchy. I remember it might be possible to successfully write non-working...

I just tried writing the wrong file ( `cpus` on a modern cpuset cgroup mount && `cpuset.cpus` on an older android kernel's noprefix mount ). Both failed permissions as root,...

> since noprefix can be set on any cgroup controller Do we need to do this for more than just the `cpuset` controller? Previous patches I've read from LXC/D only...

ping @cyphar -- opinions on https://github.com/opencontainers/runc/pull/2090#issuecomment-517859203?

Maybe executing the binary with a detach flag could be good? Return code would naturally reflect whether the application is running properly in the provider. The provider (k8s/swarm/aci) could decide...

@brendanburns just off the top of my head, The user could set up the metaparticle binary to run in GCB via CI with the cloud-builders/docker image, but this sounds like...

Related: **How is metaparticle expected to interact with CI/CD? #49**

Looks like @xfernando's code implements Option 2. One other interesting note from @jessfraz's is that since this uses `go tool`, you need access to the source code. This works fine...