Signed-off-by: Shawn Chen <chen8132@gmail.com>

Signed-off-by: Vishesh Jindal <vishesh92@gmail.com>

Signed-off-by: Shawnpku <chen8132@gmail.com>

Signed-off-by: J. Gregory Rebholz <gregrebholz@gmail.com>

Config parameter is user facing so should be documented.

Signed-off-by: Ryan Abrams <rdabrams@gmail.com>

Change-Id: I195f29195f999e3e14ba921fd3435a6dc4788417
Signed-off-by: Li Yi <denverdino@gmail.com>

Signed-off-by: Andrey Kostov <kostov.andrey@gmail.com>

Signed-off-by: Manish Tomar <manish.tomar@docker.com>

Signed-off-by: Andrew Leung <anwleung@gmail.com>

This is done by draining the connections for configured time after registry receives a SIGTERM signal.
This adds a `draintimeout` setting under `HTTP`. Registry doesn't drain
if draintimeout is not provided.

Signed-off-by: Manish Tomar <manish.tomar@docker.com>

Signed-off-by: Andrew Leung <anwleung@gmail.com>

Signed-off-by: elsanli(李楠) <elsanli@tencent.com>

at the first iteration, only the following metrics are collected:

  - HTTP metrics of each API endpoint
  - cache counter for request/hit/miss
  - histogram of storage actions, including:
    GetContent, PutContent, Stat, List, Move, and Delete

Signed-off-by: tifayuki <tifayuki@gmail.com>

This adds a configuration setting `HTTP.TLS.LetsEncrypt.Hosts` which can
be set to a list of hosts that the registry will whitelist for retrieving
certificates from Let's Encrypt. HTTPS connections with SNI hostnames
that are not whitelisted will be closed with an "unknown host" error.
It is required to avoid lots of unsuccessful registrations attempts that
are triggered by malicious clients connecting with bogus SNI hostnames.

NOTE: Due to a bug in the deprecated vendored rsc.io/letsencrypt library
clearing the host list requires deleting or editing of the cachefile to
reset the hosts list to null.

Signed-off-by: Felix Buenemann <felix.buenemann@gmail.com>

port of #2473

Signed-off-by: Viktor Stanchev <me@viktorstanchev.com>

Signed-off-by: tifayuki <tifayuki@gmail.com>

If htpasswd authentication option is configured but the htpasswd file is
missing, populate it with a default user and automatically generated
password.
The password will be printed to stdout.

Signed-off-by: Liron Levin <liron@twistlock.com>

Signed-off-by: Masataka Mizukoshi <m.mizukoshi.wakuwaku@gmail.com>

Fixed #htpasswd link

Signed-off-by: Luis Lobo Borobia <luislobo@gmail.com>

Signed-off-by: Masataka Mizukoshi <m.mizukoshi.wakuwaku@gmail.com>

Signed-off-by: Misty Stanley-Jones <misty@docker.com>

Signed-off-by: Joao Fernandes <joao.fernandes@docker.com>

Signed-off-by: Antonio Murdaca <runcom@redhat.com>

Signed-off-by: Richard Scothern <richard.scothern@docker.com>

Some frontmatter such as the weights, menu stuff, etc is no longer used
'draft=true' becomes 'published: false'

Signed-off-by: Misty Stanley-Jones <misty@docker.com>

Signed-off-by: Misty Stanley-Jones <misty@docker.com>

Signed-off-by: John Mulhausen <john@docker.com>

The Hub registry generates a large volume of notifications, many of
which are uninteresting based on target media type.  Discarding them
within the notification endpoint consumes considerable resources that
could be saved by discarding them within the registry.  To that end,
this change adds registry configuration options to restrict the
notifications sent to an endpoint based on target media type.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>

Access logging is great.  Access logging you can turn off is even
better.  This change adds a configuration option for that.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>

Let's Encrypt uses tls-sni to validate the certificate
on the standard https port 443. If the registry is
outwardly listening on a different port Let's Encrypt
will not issue a certificate.

Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)

This change to the S3 Move method uses S3's multipart upload API to copy
objects whose size exceeds a threshold.  Parts are copied concurrently.
The level of concurrency, part size, and threshold are all configurable
with reasonable defaults.

Using the multipart upload API has two benefits.

* The S3 Move method can now handle objects over 5 GB, fixing #886.

* Moving most objects, and espectially large ones, is faster.  For
  example, moving a 1 GB object averaged 30 seconds but now averages 10.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>

Http2 will be enabled by default and can be disabled with a configuration option.

Signed-off-by: Adam Duke <adam.v.duke@gmail.com>

Until we have some experience hosting foreign layer manifests, the Hub
operators wish to limit foreign layers on Hub. To that end, this change
adds registry configuration options to restrict the URLs that may appear
in pushed manifests.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>

Signed-off-by: Richard Scothern <richard.scothern@docker.com>

Signed-off-by: allencloud <allen.sun@daocloud.io>

And move menu entry definition into a page that the user has no reason to navigate to

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>

pull.

Signed-off-by: Richard Scothern <richard.scothern@docker.com>

Signed-off-by: Tony Holdstock-Brown <tony@docker.com>

Signed-off-by: Andrew Hsu <andrewhsu@acm.org> (github: andrewhsu)

Signed-off-by: Mary Anthony <mary@docker.com>