mirror of
https://github.com/project-zot/zot.git
synced 2025-03-04 02:02:49 -05:00
aaee0220e4
when a client pushes an image zot's inline dedupe will try to find the blob path corresponding with the blob digest that it's currently pushed and if it's found in the cache then zot will make a symbolic link to that cache entry and report to the client that the blob already exists on the location. Before this patch authorization was not applied on this process meaning that a user could copy blobs without having permissions on the source repo. Added a rule which says that the client should have read permissions on the source repo before deduping, otherwise just Stat() the blob and return the corresponding status code. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> Co-authored-by: Petu Eusebiu <peusebiu@cisco.com> |
||
|---|---|---|
| .. | ||
| cache | ||
| common | ||
| constants | ||
| gc | ||
| 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