d0e396aa60
Because the lock on an ingest ref being held regardless of whether a writer was in use, resuming an existing ingest proved impossible. We now defer writer locking to the content store backend, where the lock will be released automatically on closing the writer or on restarting containerd. There are still cases where a writer can be abandoned but not closed, leaving an active ingest, but this is extremely rare and can be resolved with a daemon restart. Signed-off-by: Stephen J Day <stephen.day@docker.com> |
||
|---|---|---|
| .. | ||
| local | ||
| testsuite | ||
| content.go | ||
| helpers.go | ||