close the io.ReadCloser from storage driver

Add docker image release workflow

Add CodeQL Security Scanning

Signed-off-by: Chris Aniszczyk <caniszczyk@gmail.com>

Signed-off-by: Milos Gajdos <milosgajdos83@gmail.com>

Signed-off-by: sangluo <sangluo@pinduoduo.com>

fix: disable DisableHTMLEscape on logrus json logging

Signed-off-by: Milos Gajdos <milosgajdos83@gmail.com>

fix CI dependency error

Fix the failure reported by git action

Package python-minimal is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python2-minimal

E: Package 'python-minimal' has no installation candidate
Signed-off-by: Wang Yan <wangyan@vmware.com>

Add code to handle pagination of parts. Fixes max layer size of 10GB bug

docs/spec/manifest-v2-2.md: fix ARM variant

log: Include configured fields in all logs

Populate the platform information when calling the References() method of manifest list

Populate the platform information when calling the References() method of manifest list
Signed-off-by: Wenkai Yin <yinw@vmware.com>

It's possible to configure log fields in the configuration file, and we would
like these fields to be included in all logs. Previously these fields were
included only in logs produced using the main routine's context, meaning that
any logs from a request handler were missing the fields since those use a
context based on the HTTP request's context.

Add a configurable default logger to the `context` package, and set it when
configuring logging at startup time.
Signed-off-by: Adam Wolfe Gordon <awg@digitalocean.com>

Fix bug in parsing domain from repository reference

Add a basic e2e test for CI

manifests: Return UNSUPPORTED when deleting manifests by tag

Added flag for user-configurable cipher suites

Thanks, @d-luu for putting the effort into this. Much appreciated!

Configuration of list of cipher suites allows a user to disable use
of weak ciphers or continue to support them for legacy usage if they
so choose.

List of available cipher suites at:
https://golang.org/pkg/crypto/tls/#pkg-constants



Default cipher suites have been updated to:
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_AES_128_GCM_SHA256
- TLS_CHACHA20_POLY1305_SHA256
- TLS_AES_256_GCM_SHA384

MinimumTLS has also been updated to include TLS 1.3 as an option
and now defaults to TLS 1.2 since 1.0 and 1.1 have been deprecated.
Signed-off-by: David Luu <david@davidluu.info>

The correct `vairant` string for ARM v6 is "v6", not "armv6l".

There is no known implementation that actually uses "armv6l".

See the discussion in opencontainers/image-spec PR 817
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

Bump Golang to `1.15`.

Signed-off-by: olegburov <oleg.burov@outlook.com>

Upgrade Logstash hook for Logrus to 1.0.0

Add Codecov badge

Fixes #3363

Without this, we emit illegal json logs, the user-agent
ends up as:

```
"http.request.useragent": "docker/19.03.4 go/go1.12.10 git-commit/9013bf583a kernel/5.10.10-051010-generic os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.4 \(linux\))"
```

which is not valid according to [spec](https://www.json.org/json-en.html

)

specifically, string: "<any codepoint except " or \ or control>*"
Signed-off-by: Don Bowman <don@agilicus.com>

Signed-off-by: olegburov <oleg.burov@outlook.com>

Signed-off-by: Tom Hu <tomhu1096@gmail.com>

go.mod: change imports to github.com/distribution/distribution/v3

Go 1.13 and up enforce import paths to be versioned if a project
contains a go.mod and has released v2 or up.

The current v2.x branches (and releases) do not yet have a go.mod,
and therefore are still allowed to be imported with a non-versioned
import path (go modules add a `+incompatible` annotation in that case).

However, now that this project has a `go.mod` file, incompatible
import paths will not be accepted by go modules, and attempting
to use code from this repository will fail.

This patch uses `v3` for the import-paths (not `v2`), because changing
import paths itself is a breaking change, which means that  the
next release should increment the "major" version to comply with
SemVer (as go modules dictate).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

Relax filesystem driver folder permissions to 0777

Update repo normalize error message to include name

Fix minor spelling mistakes

scripts: remove unused md2man from dev-tools

Update README

Remove apache2-utils from Dockerfile