mirror of
https://github.com/project-zot/zot.git
synced 2025-01-20 22:52:51 -05:00
5494a1b8d6
when pushing manifests, zot will validate blobs (layers + config blob) are present in repo, currently it opens(in case of filesystem storage) or download( in case of cloud storage) each blob. fixed that by adding a new method ImageStore.CheckBlobPresence() on storage to check blobs presence without checking the cache like ImageStore.CheckBlob() method does. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> |
||
---|---|---|
.. | ||
cache | ||
common | ||
constants | ||
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