mirror of
https://github.com/project-zot/zot.git
synced 2025-04-01 02:42:32 -05:00
Suppose we push two identical manifests (sharing same digest) but with different tags, then deleting by digest should throw an error otherwise we end up deleting all image tags (with gc) or dangling references (without gc) This behaviour is controlled via Authorization, added a new policy action named detectManifestsCollision which enables this behaviour Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com> Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> Co-authored-by: Ramkumar Chinchani <rchincha@cisco.com> |
||
---|---|---|
.. | ||
cache | ||
constants | ||
local | ||
s3 | ||
cache.go | ||
cache_test.go | ||
common.go | ||
common_test.go | ||
lint-interface.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