mirror of
https://github.com/project-zot/zot.git
synced 2026-06-17 21:17:58 +08:00
e7a5e09214
It is to fix #3185. This fixes the case where MetaDB is not instantiated (none of the conditions match), and we want to retain tags only by pattern (which should not need to use MetaBD). Without this fix you could only use retention to delete untagged manifests. If you specified only the key "patterns" under "keepTags", zot would crash. It was possible to not specify "keepTags" all, which would retain all tags, but it was not possible to retains specific tags. Basically the case quoted below, from the documentation, was broken:: https://zotregistry.dev/v2.1.4/articles/retention/#configuration-example ``` When you specify a regex pattern with no rules other than the default, all tags matching the pattern are retained. ``` This would only work if MetaDb was instantiated by an unrelated configured feature. Signed-off-by: Andrei Aaron <aaaron@luxoft.com>
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