Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: added config for docker2s2, plus What's New for v2.1.2 #185

Merged
merged 1 commit into from
Dec 15, 2024
Merged

docs: added config for docker2s2, plus What's New for v2.1.2 #185

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/admin-guide/admin-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ The configuration file is a JSON or YAML file that contains all configuration se
- logging
- metrics
- synchronization with other registries
-
- clustering

The zot service is initiated with the `zot serve` command followed by the name of a configuration file, as in this example:
Expand Down Expand Up @@ -379,6 +380,23 @@ The following table lists the configurable attributes of the `lint` extension.
If the mandatory annotations option is configured when you push an image, linter will verify that the mandatory annotations list present in the configuration is also found in the manifest's annotations list. If any annotations are missing, the push is denied.


<a name="compat_config"></a>

## Compatibility with other image schema types

As an option, zot can be configured to store images using the schema [Docker Manifest v2 Schema v2](https://distribution.github.io/distribution/spec/manifest-v2-2/). In this case, a Docker image can be copied to zot without modifications to the image's manifest or digest. Such modifications would otherwise break the image's signature and attestations.

To enable this compatibility, configure the `compat` attribute under `http` in the zot configuration file. Set the `compat` value to `docker2s2` as shown in the following example:

```json
"http": {
"address": "127.0.0.1",
"port": "8080",
"compat": ["docker2s2"]
}
```


<a name="trust_config"></a>

## Verifying the signatures of uploaded images
Expand Down
6 changes: 6 additions & 0 deletions docs/general/whats-new.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# What's New

## [v2.1.2](https://github.com/project-zot/zot/releases/tag/v2.1.2)

### Compatibility with other image schema types

A new configuration setting allows you to store images using the schema [Docker Manifest v2 Schema v2](https://distribution.github.io/distribution/spec/manifest-v2-2/). With this setting enabled, zot makes no modifications to the image's manifest or digest. Such modifications would otherwise break the image's signature and attestations.

## [v2.1.0](https://github.com/project-zot/zot/releases/tag/v2.1.0)

### Scale-out cluster
Expand Down
Loading