mirror of
https://github.com/project-zot/zot.git
synced 2024-12-16 21:56:37 -05:00
b80deb9927
unified both local and s3 ImageStore logic into a single ImageStore added a new driver interface for common file/dirs manipulations to be implemented by different storage types refactor(gc): drop umoci dependency, implemented internal gc added retentionDelay config option that specifies the garbage collect delay for images without tags this will also clean manifests which are part of an index image (multiarch) that no longer exist. fix(dedupe): skip blobs under .sync/ directory if startup dedupe is running while also syncing is running ignore blobs under sync's temporary storage fix(storage): do not allow image indexes modifications when deleting a manifest verify that it is not part of a multiarch image and throw a MethodNotAllowed error to the client if it is. we don't want to modify multiarch images Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> |
||
|---|---|---|
| .. | ||
| cache | ||
| common | ||
| constants | ||
| imagestore | ||
| local | ||
| s3 | ||
| types | ||
| cache.go | ||
| cache_benchmark_test.go | ||
| cache_test.go | ||
| README.md | ||
| scrub.go | ||
| scrub_test.go | ||
| storage.go | ||
| storage_controller.go | ||
| storage_test.go | ||
zot currently supports two types of underlying filesystems:
-
local - a locally mounted filesystem
-
remote - a remote filesystem such as AWS S3
The cache database can be configured independently of storage. Right now, zot supports the following database implementations:
- BoltDB - local storage. Set the "cloudCache" field in the config file to false. Example: examples/config-boltdb.json