diff --git a/datacenter/dtr/2.3/guides/admin/configure/deploy-caches/tls.md b/datacenter/dtr/2.3/guides/admin/configure/deploy-caches/tls.md index 3cf8570e3d..0ea8cccbf6 100644 --- a/datacenter/dtr/2.3/guides/admin/configure/deploy-caches/tls.md +++ b/datacenter/dtr/2.3/guides/admin/configure/deploy-caches/tls.md @@ -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: /config.yml + docker/dtr-content-cache:{{ page.dtr_version_patch }} /config.yml ``` ## Use Let's Encrypt diff --git a/datacenter/dtr/2.3/guides/admin/configure/external-storage/index.md b/datacenter/dtr/2.3/guides/admin/configure/external-storage/index.md index ffe90d9cd0..b542e6ea53 100644 --- a/datacenter/dtr/2.3/guides/admin/configure/external-storage/index.md +++ b/datacenter/dtr/2.3/guides/admin/configure/external-storage/index.md @@ -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-` to store +By default, DTR creates a volume named `dtr-registry-` 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- # Check the disk usage -du -hs +sudo du -hs \ +$(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-)) ``` ## NFS diff --git a/datacenter/dtr/2.3/guides/admin/configure/external-storage/nfs.md b/datacenter/dtr/2.3/guides/admin/configure/external-storage/nfs.md index db368e1519..ba338b6e7d 100644 --- a/datacenter/dtr/2.3/guides/admin/configure/external-storage/nfs.md +++ b/datacenter/dtr/2.3/guides/admin/configure/external-storage/nfs.md @@ -31,7 +31,7 @@ mkdir /tmp/mydir && sudo mount -t nfs : 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 \ ``` @@ -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 ``` @@ -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 "" ``` diff --git a/datacenter/dtr/2.3/guides/admin/configure/set-up-vulnerability-scans.md b/datacenter/dtr/2.3/guides/admin/configure/set-up-vulnerability-scans.md index 5425a56cf2..7c173ab3df 100644 --- a/datacenter/dtr/2.3/guides/admin/configure/set-up-vulnerability-scans.md +++ b/datacenter/dtr/2.3/guides/admin/configure/set-up-vulnerability-scans.md @@ -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: - +4. Locate your Docker EE Advanced subscription or trial. +5. Click **Setup** button. + + ![](../../images/cve-file-1.png){: .with-border} + +6. Click **Download CVE Vulnerability Database** link to download the database file. + + ![](../../images/cve-file-2.png){: .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: diff --git a/datacenter/dtr/2.3/guides/admin/upgrade.md b/datacenter/dtr/2.3/guides/admin/upgrade.md index 01b05ce777..d32dd280c2 100644 --- a/datacenter/dtr/2.3/guides/admin/upgrade.md +++ b/datacenter/dtr/2.3/guides/admin/upgrade.md @@ -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. -> **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 diff --git a/datacenter/dtr/2.3/guides/images/cve-file-1.png b/datacenter/dtr/2.3/guides/images/cve-file-1.png new file mode 100644 index 0000000000..5d861dbfc3 Binary files /dev/null and b/datacenter/dtr/2.3/guides/images/cve-file-1.png differ diff --git a/datacenter/dtr/2.3/guides/images/cve-file-2.png b/datacenter/dtr/2.3/guides/images/cve-file-2.png new file mode 100644 index 0000000000..ea820ec7b8 Binary files /dev/null and b/datacenter/dtr/2.3/guides/images/cve-file-2.png differ diff --git a/datacenter/dtr/2.3/guides/release-notes/incompatibilities-and-breaking-changes.md b/datacenter/dtr/2.3/guides/release-notes/incompatibilities-and-breaking-changes.md index eeb4f0effb..589ce1c900 100644 --- a/datacenter/dtr/2.3/guides/release-notes/incompatibilities-and-breaking-changes.md +++ b/datacenter/dtr/2.3/guides/release-notes/incompatibilities-and-breaking-changes.md @@ -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` diff --git a/datacenter/dtr/2.3/guides/release-notes/index.md b/datacenter/dtr/2.3/guides/release-notes/index.md index 34736166a9..64bc6b1569 100644 --- a/datacenter/dtr/2.3/guides/release-notes/index.md +++ b/datacenter/dtr/2.3/guides/release-notes/index.md @@ -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 - - ![](../images/release-notes-1.png) - -**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. diff --git a/datacenter/dtr/2.3/guides/support.md b/datacenter/dtr/2.3/guides/support.md index 660252beb0..c48c7dd09d 100644 --- a/datacenter/dtr/2.3/guides/support.md +++ b/datacenter/dtr/2.3/guides/support.md @@ -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 --- - - Your Docker Data Center, or Docker Trusted Registry subscription gives you access to prioritized support. The service levels depend on your subscription. diff --git a/datacenter/dtr/2.3/guides/user/manage-images/sign-images/manage-trusted-repositories.md b/datacenter/dtr/2.3/guides/user/manage-images/sign-images/manage-trusted-repositories.md index 3708d4f656..64995e274d 100644 --- a/datacenter/dtr/2.3/guides/user/manage-images/sign-images/manage-trusted-repositories.md +++ b/datacenter/dtr/2.3/guides/user/manage-images/sign-images/manage-trusted-repositories.md @@ -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