baaf7543dc
Bring the content service into the containerd API. This allows the content store to be coordinated in the containerd daemon with minimal effort. For the most part, this API follows the conventions and behavior of the existing content store implementation with a few caveats. Specifically, we remove the object oriented transaction mechanism in favor of a very rich `Write` call. Pains are taken to reduce race conditions around when having multiple writers to a single piece of content. Clients should be able to race towards getting a write lock on a reference, then wait on each other. For the most part, this should be generically pluggable to allow implementations of the content store to be swapped out. We'll follow this up with an implementation to validate the model. Signed-off-by: Stephen J Day <stephen.day@docker.com> |
||
|---|---|---|
| .. | ||
| content | ||
| execution | ||
| shim | ||