mirror of https://github.com/containers/podman.git
b10beb5395
Lock access to and modification of the index.json file, to ensure concurrent addition/removal does not result in lost state. Use a standard c/storage lockfile, making use of its r/w locking ability to support concurrent access, only serializing writes. This is not a very efficient locking scheme around artifact removal and - especially - addition. I view this as the first step, establishing any sort of mutual exclusion to prevent state corruption. Step 2 is to adapt the staged removal work being done to make image removal require only minimal use of locks, ensuring it works with artifact addition. This staged addition means we won't have to hold the lock for the full artifact pull. Signed-off-by: Matt Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| store | ||
| types | ||
| artifact.go | ||