mirror of https://github.com/docker/docs.git
Update DTR to 2.3
This commit is contained in:
Joao Fernandes
Jim Galasyn
parent
c70a713b61
commit
e10907abd4
|
|
@ -75,7 +75,7 @@ docker run --detach --restart always \
|
|||
--volume $(pwd)/dtr-cache-key.pem:/certs/dtr-cache-key.pem \
|
||||
--volume $(pwd)/dtr-ca.pem:/certs/dtr-ca.pem \
|
||||
--volume $(pwd)/config.yml:/config.yml \
|
||||
docker/dtr-content-cache:<version> /config.yml
|
||||
docker/dtr-content-cache:{{ page.dtr_version_patch }} /config.yml
|
||||
```
|
||||
|
||||
## Use Let's Encrypt
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: Configure DTR image storage
|
||||
description: Storage configuration for Docker Trusted Registry
|
||||
keywords: docker, documentation, about, technology, understanding, configuration,
|
||||
storage, storage drivers, Azure, S3, Swift, enterprise, hub, registry
|
||||
title: Configure DTR image storage
|
||||
---
|
||||
|
||||
By default DTR uses the local filesystem of the node where it is running to
|
||||
|
|
@ -40,7 +40,7 @@ The format of this configuration file is similar to the one used by
|
|||
|
||||
## Local filesystem
|
||||
|
||||
By default, DTR creates a volume names `dtr-registry-<replica-id>` to store
|
||||
By default, DTR creates a volume named `dtr-registry-<replica-id>` to store
|
||||
your images using the local filesystem. You can customize the name and path of
|
||||
the volume used by DTR, using the `docker/dtr reconfigure --dtr-storage-volume`
|
||||
option.
|
||||
|
|
@ -57,7 +57,8 @@ can ssh into the node where DTR is deployed and run:
|
|||
docker volume inspect dtr-registry-<replica-id>
|
||||
|
||||
# Check the disk usage
|
||||
du -hs <path-to-volume>
|
||||
sudo du -hs \
|
||||
$(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-<dtr-replica>))
|
||||
```
|
||||
|
||||
## NFS
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ mkdir /tmp/mydir && sudo mount -t nfs <nfs server>:<directory>
|
|||
One way to configure DTR to use an NFS directory is at install time:
|
||||
|
||||
```none
|
||||
docker run -it --rm docker/dtr install \
|
||||
docker run -it --rm docker/dtr:{{ dtr_version_patch }} install \
|
||||
--nfs-storage-url <nfs-storage-url> \
|
||||
<other options>
|
||||
```
|
||||
|
|
@ -50,7 +50,7 @@ If you want to start using the new DTR built-in support for NFS you can
|
|||
reconfigure DTR:
|
||||
|
||||
```none
|
||||
docker run -it --rm docker/dtr reconfigure \
|
||||
docker run -it --rm docker/dtr:{{ dtr_version_patch }} reconfigure \
|
||||
--nfs-storage-url <nfs-storage-url>
|
||||
```
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ If you want to reconfigure DTR to stop using NFS storage, leave the option
|
|||
in blank:
|
||||
|
||||
```none
|
||||
docker run -it --rm docker/dtr reconfigure \
|
||||
docker run -it --rm docker/dtr:{{ dtr_version_patch}} reconfigure \
|
||||
--nfs-storage-url ""
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -139,20 +139,27 @@ Your choice is saved automatically.
|
|||
|
||||
### Update CVE database - offline mode
|
||||
|
||||
To update the CVE database for your DTR instance when it cannot contact the update server, you download and install a `.tar` file that contains the database updates. Contact us at [nautilus-feedback@docker.com](mailto:nautilus-feedback@docker.com?Subject=Need%20CVE%20database%20file) for an updated database file.
|
||||
To update the CVE database for your DTR instance when it cannot contact the update server, you download and install a `.tar` file that contains the database updates. To download the file:
|
||||
|
||||
<!-- TODO: update when Store updates available: https://docker.atlassian.net/browse/MER-1444
|
||||
1. Log in to the Docker Store.
|
||||
1. Log in to the [Docker Store](https://store.docker.com/).
|
||||
|
||||
If you are a member of an Organization managing licenses using Docker Store,
|
||||
make sure your account is a member of the `Owners` team. Only Owners can
|
||||
view and manage licenses and other entitlements for Organizations from the
|
||||
Docker Store.
|
||||
|
||||
2. In the top right corner, click your user account icon, and select **Subscriptions**.
|
||||
2. In the top right corner, click your user account icon, and select **My Content**.
|
||||
3. If necessary, select an organization account from the **Accounts** menu at the upper right.
|
||||
4. Locate Docker Datacenter in the **Subscriptions** list.
|
||||
5. Click ...-->
|
||||
4. Locate your Docker EE Advanced subscription or trial.
|
||||
5. Click **Setup** button.
|
||||
|
||||
{: .with-border}
|
||||
|
||||
6. Click **Download CVE Vulnerability Database** link to download the database file.
|
||||
|
||||
{: .with-border}
|
||||
|
||||
If you run into problems, contact us at nautilus-feedback@docker.com for the file.
|
||||
|
||||
To manually update the DTR CVE database from a `.tar` file:
|
||||
|
||||
|
|
|
|||
|
|
@ -41,15 +41,14 @@ Before starting your upgrade planning, make sure that the version of UCP you are
|
|||
using is supported by the version of DTR you are trying to upgrade to. <!--(TODO:
|
||||
link to the compatibility matrix)-->
|
||||
|
||||
> **Warning**
|
||||
> Backup DTR before upgrading
|
||||
>
|
||||
> Before performing any upgrade it’s important to backup. See
|
||||
> [DTR backups and recovery](/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md).
|
||||
{: .warning}
|
||||
|
||||
### Step 1. Upgrade DTR to 2.1 if necessary
|
||||
### Step 1. Upgrade DTR to 2.2 if necessary
|
||||
|
||||
Make sure you're running DTR 2.1. If that's not the case, [upgrade your installation to the 2.1 version](/datacenter/dtr/2.1/guides/install/upgrade/.md).
|
||||
Make sure you're running DTR 2.2. If that's not the case, [upgrade your installation to the 2.2 version](/datacenter/dtr/2.2/guides/admin/upgrade.md).
|
||||
|
||||
### Step 2. Upgrade DTR
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 344 KiB |
|
|
@ -2,8 +2,6 @@
|
|||
title: Incompatibilities and breaking changes
|
||||
description: Learn about the incompatibilities and breaking changes introduced by Docker Trusted Registry version {{ page.dtr_version_minor }}
|
||||
keywords: docker, ucp, upgrade, incompatibilities
|
||||
redirect_from:
|
||||
- /datacenter/dtr/2.2/guides/admin/upgrade/incompatibilities-and-breaking-changes/
|
||||
---
|
||||
|
||||
With Docker Trusted Registry {{ page.dtr_version_minor }}, the `/load_balancer_status`
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: DTR {{ page.dtr_version_minor }} release notes
|
||||
description: Learn about the new features, bug fixes, and breaking changes for Docker Trusted Registry {{ page.dtr_version_minor }}
|
||||
keywords: docker trusted registry, whats new, release notes
|
||||
redirect_from:
|
||||
- /datacenter/dtr/2.2/guides/admin/upgrade/release-notes/
|
||||
---
|
||||
|
||||
Here you can learn about new features, bug fixes, breaking changes and
|
||||
|
|
@ -11,145 +9,3 @@ known issues for each DTR version.
|
|||
|
||||
You can then use [the upgrade instructions](../admin/upgrade.md),
|
||||
to upgrade your installation to the latest release.
|
||||
|
||||
## DTR 2.2.4
|
||||
|
||||
(13 April 2017)
|
||||
|
||||
**Bugs fixed**
|
||||
|
||||
* High impact
|
||||
* Fixed memory leaks causing DTR to use all RAM available
|
||||
* Fixed concurrency problems that might cause the registry and api server to
|
||||
restart
|
||||
* Improved performance of search on the web UI. To improve performance
|
||||
the search now only returns accounts and repositories that match the search
|
||||
input. It no longer shows repositories belonging to the accounts returned in
|
||||
the search result
|
||||
* The web UI now displays all members of an organization
|
||||
* Low impact
|
||||
* When installing or joining replicas with `--nfs-storage-url` and the
|
||||
installation fails, DTR now deletes the `.dtr-nfs-test` file
|
||||
* The web UI now shows if a team is managed in LDAP or not
|
||||
* After updating the vulnerability database, a rescan button only shows
|
||||
if the user has permissions for that action
|
||||
|
||||
|
||||
## DTR 2.2.3
|
||||
|
||||
(9 March 2017)
|
||||
|
||||
**New features**
|
||||
|
||||
* The tags list API now supports pagination
|
||||
|
||||
**General improvements**
|
||||
|
||||
* Several improvements to the installer to make it more resilient
|
||||
* Improved the installer to better detect port conflicts when installing or joining DTR replicas
|
||||
* Security scans can now be canceled
|
||||
* DTR job logs are now stored in the DTR datastore but also sent to Docker Engine
|
||||
|
||||
**Bugs fixed**
|
||||
|
||||
* Fixed an issue introduced in 2.2.2 that caused the scanning button to not be
|
||||
displayed for images that had never been scanned
|
||||
* Fixed memory leaks in the DTR API server and Registry containers
|
||||
|
||||
## DTR 2.2.2
|
||||
|
||||
(27 Feb 2017)
|
||||
|
||||
**New features**
|
||||
|
||||
* The web UI now displays a banner to administrators when a tag migration job
|
||||
is running
|
||||
|
||||
|
||||
|
||||
**General improvements**
|
||||
|
||||
* Upgraded DTR security scanner
|
||||
* Security scanner now generates less verbose logs
|
||||
* Made `docker/dtr join` more resilient when using an NFS storage backend
|
||||
* Made tag migrations more stable
|
||||
* Made updates to the vulnerability database more stable
|
||||
|
||||
**Bugs fixed**
|
||||
|
||||
* Fixed a problem when trying to use Scality as storage backend. This problem
|
||||
affected DTR 2.2.0 and 2.2.1
|
||||
* You can now use the web UI to create and manage teams that have slashes in
|
||||
their name
|
||||
* Fixed an issue causing RethinkDB to not start due to DNS errors when
|
||||
the RethinkDB containers were not restarted at the same time
|
||||
* The web UI now shows the security scanning button if the vulnerability database
|
||||
or security scanner have been updated
|
||||
|
||||
|
||||
## DTR 2.2.1
|
||||
|
||||
(9 Feb 2017)
|
||||
|
||||
**Bugs fixed**
|
||||
|
||||
* Webhooks triggered on a security scan now have information about vulnerabilities
|
||||
* The web UI now displays tag details and security scanning information for
|
||||
images pushed before the upgrade
|
||||
* When multiple tags shared the same manifest, the UI only displayed a single
|
||||
tag. This has been fixed
|
||||
* Fixed the UI not correctly showing the Dockerfile for tags in migrated
|
||||
repositories
|
||||
|
||||
## DTR 2.2.0
|
||||
|
||||
(9 Feb 2017)
|
||||
|
||||
**New features**
|
||||
|
||||
* DTR can now scan the binaries contained in the image layers, and report
|
||||
security vulnerabilities
|
||||
* You can now configure multiple caches, so that users can pull images faster
|
||||
* You can now configure webhooks to run automated tasks that are triggered by
|
||||
events like image push, repository creation, and others
|
||||
|
||||
**General improvements**
|
||||
|
||||
* UI/UX
|
||||
* Improved error messages to be more meaningful and help troubleshoot the problem
|
||||
* Several UI/UX improvements to the DTR configuration page and user settings page
|
||||
* Several improvements to the search bar used in the UI
|
||||
|
||||
* docker/dtr image
|
||||
* The `docker/dtr install` command now shows all the nodes that are part of a
|
||||
UCP cluster for you choose on which node to deploy DTR
|
||||
* The install command was improved to avoid deploying DTR to a node where it
|
||||
cannot run due to port collisions
|
||||
* The `docker/dtr install --ucp-node` flag is now mandatory
|
||||
* The install command no longer allows deploying replicas with duplicate ids
|
||||
* The upgrade command now validates if all tags were migrated to the latest
|
||||
version before trying to migrate blob links
|
||||
|
||||
**Bugs fixed**
|
||||
|
||||
* When creating a repository, the length of the repository now is consistent
|
||||
between the UI and API
|
||||
* The UI now validate and doesn't allow creating repository names with uppercase
|
||||
letters
|
||||
* You can now create organizations with dashes in the name
|
||||
* Fixed a bug that didn't allow deleting users immediately after they were
|
||||
created
|
||||
* The copy to clipboard button on the repository page now works on Firefox
|
||||
* The repository page now renders properly the repository permissions
|
||||
* You can now delete a users full name from the UI
|
||||
* Organization administrators can now see the repositories owned by the organization
|
||||
* The garbage collection settings now show the correct cron values
|
||||
* You can now specify DTR to use port 443 when installing DTR
|
||||
* When you don't have permissions to see the repository details, the UI now
|
||||
shows that you don't have permissions instead of saying it has no manifests
|
||||
* Jobs are retried if the worker running them stops unexpectedly
|
||||
|
||||
**Deprecation**
|
||||
|
||||
The `/load_balancer_status` is deprecated and is going to be removed in future
|
||||
versions. Use the `/health` endpoint instead.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,10 @@
|
|||
---
|
||||
title: Get support for DTR
|
||||
description: Your Docker subscription gives you access to prioritized support. You
|
||||
can file tickets via email, your the support portal.
|
||||
keywords: Docker, support, help
|
||||
title: Get support for DTR
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Your Docker Data Center, or Docker Trusted Registry subscription gives you
|
||||
access to prioritized support. The service levels depend on your subscription.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: Manage trusted repositories
|
||||
description: Learn how to use the Notary CLI client to manage trusted repositories
|
||||
keywords: dtr, trust, notary, security
|
||||
redirect_from:
|
||||
- /datacenter/dtr/2.2/guides/user/manage-images/manage-trusted-repositories/
|
||||
---
|
||||
|
||||
Once you
|
||||
|
|
|
|||
Loading…
Reference in New Issue