diff --git a/_data/toc.yaml b/_data/toc.yaml index e34d917558..21c72805b6 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -2537,7 +2537,7 @@ manuals: title: Create promotion policies - path: /datacenter/dtr/2.4/reference/api/ title: API reference - - path: /datacenter/dtr/2.4/guides/release-notes/ + - path: /ee/dtr/release-notes/ title: Release notes - path: /datacenter/dtr/2.4/guides/support/ title: Get support diff --git a/datacenter/dtr/2.4/guides/release-notes.md b/datacenter/dtr/2.4/guides/release-notes.md deleted file mode 100644 index cf9ca90435..0000000000 --- a/datacenter/dtr/2.4/guides/release-notes.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: DTR 2.4 release notes -description: Learn about the new features, bug fixes, and breaking changes for Docker Trusted Registry -keywords: docker trusted registry, whats new, release notes -toc_max: 2 ---- - -> **DTR 2.5 now available**. [You can check the release notes here](/ee/dtr/release-notes.md). - -Here you can learn about new features, bug fixes, breaking changes, and -known issues for each patch release of DTR 2.4. -You can then use [the upgrade instructions](admin/upgrade.md), -to upgrade your installation to the latest release. - -## Version 2.4.3 (2018-03-19) - -**Security** - -* Dependencies updated to consume upstream CVE patches. - -## Version 2.4.2 (13 February 2018) - -**Security notice** - -The log driver is now disabled for containers started by backup and HA cluster -join operations. This is a critical security fix for customers that rely on -Docker Trusted Registry 2.2, 2.3 and 2.4 with a log driver to capture logs from -all containers across the platform. - -Caution is advised when applying this update, make sure you redeploy DTR, and in -the process you will create new credentials because the previous ones were -potentially disclosed due to the vulnerability. - -Use the `--log-driver=none` option for `docker run` when running a DTR backup, HA -cluster join or dumpcerts. - -## 2.4.1 (20 November 2017) - -**Bug fixes** - -* Fixed a bug that cause certain vulnerabilities to not be found during scanning. -* Increased speed of lock expiration in case of failed joins. -* Fixed notification when toggling active status of webhooks. -* Speed up detection of dead jobrunners. -* Fixed a bug where garbage collection ran in a suboptimal mode if scheduled as -a cron from the UI. -* Fixed a potential issue with the way we untar files in uploads of the -vulnerability database. -* Fixed scanning issue with some windows images. -* Fixed a bug with not backing up repository team permissions correctly. - -**General improvements** - -* Improved resilience of garbage collection. -* Improved logging of garbage collection. -* Improved memory usage during backup. -* Improved error handling when uploading invalid vulnerability databases. -* Improve resilience of DTR join operations. -* Hide secrets on storage config pages. - -**Deprecations** - -* The `api/v0/imagescan/layer/{layerid}` endpoint is deprecated, and will be -removed in DTR 2.5. You can use the -`/api/v0/imagescan/repositories/{namespace}/{reponame}/{tag}` endpoint instead. - - -## DTR 2.4.0 (2 November 2017) - -**New features** - -* Upgraded to Swagger 2.0 and Swagger UI 3.0. -* DTR can now be deployed on IBM Z (s390x architecture). -* Updated the `docker/dtr-rethink` images to include `rethinkcli` for easier troubleshooting. -* Notary now allows you to see audit logs using the `/v2/_trust/changefeed`, and -`/v2//_trust/changefeed` endpoints. - -**Bug fixes** - -* When setting up periodic garbage collection, it used to run in a different, -less thorough mode than when run manually. Now garbage collection always runs in -the correct mode. -* Fix error when garbage collecting manifest lists. -* Fixed issue when reconfiguring DTR from a non-local storage to NFS, causing the -change to not be persisted. -* Backported Docker Distribution race fix. [2299](https://github.com/docker/distribution/pull/2299) -* Reduced unnecessary logs in Jobrunner. -* Other general reliability improvements. - -**Known issues** - -* Backup uses too much memory and can cause out of memory issues for large databases. -* The `--nfs-storage-url` option uses the system's default NFS version instead -of testing the server to find which version works. diff --git a/ee/dtr/release-notes.md b/ee/dtr/release-notes.md index 7ed1d1809a..f1006d6333 100644 --- a/ee/dtr/release-notes.md +++ b/ee/dtr/release-notes.md @@ -4,6 +4,7 @@ description: Learn about the new features, bug fixes, and breaking changes for D keywords: docker trusted registry, whats new, release notes toc_max: 2 redirect_from: + - /datacenter/dtr/2.4/guides/release-notes/ - /datacenter/dtr/2.5/guides/release-notes/ --- @@ -100,23 +101,89 @@ specify `--log-protocol`. image has a layer over 100MB. * On upgrade the scanningstore container may restart with this error message: - ``` - The data directory was initialized by PostgreSQL version 9.6, - which is not compatible with this version 10.3. - ``` - To remedy this remove the scanningstore container and the dtr-postgres volume, and perform a reconfigure - ``` - docker stop dtr-scanningstore-$replica - docker rm dtr-scanningstore-$replica - docker volume rm dtr-postgres-$replica - docker run --rm -it docker/dtr:2.5.0 reconfigure ... - ``` - Then resync the vulnerability database from the web UI. +## Version 2.4.3 (2018-03-19) +**Security** + +* Dependencies updated to consume upstream CVE patches. + +## Version 2.4.2 (13 February 2018) + +**Security notice** + +The log driver is now disabled for containers started by backup and HA cluster +join operations. This is a critical security fix for customers that rely on +Docker Trusted Registry 2.2, 2.3 and 2.4 with a log driver to capture logs from +all containers across the platform. + +Caution is advised when applying this update, make sure you redeploy DTR, and in +the process you will create new credentials because the previous ones were +potentially disclosed due to the vulnerability. + +Use the `--log-driver=none` option for `docker run` when running a DTR backup, HA +cluster join or dumpcerts. + +## 2.4.1 (20 November 2017) + +**Bug fixes** + +* Fixed a bug that cause certain vulnerabilities to not be found during scanning. +* Increased speed of lock expiration in case of failed joins. +* Fixed notification when toggling active status of webhooks. +* Speed up detection of dead jobrunners. +* Fixed a bug where garbage collection ran in a suboptimal mode if scheduled as +a cron from the UI. +* Fixed a potential issue with the way we untar files in uploads of the +vulnerability database. +* Fixed scanning issue with some windows images. +* Fixed a bug with not backing up repository team permissions correctly. + +**General improvements** + +* Improved resilience of garbage collection. +* Improved logging of garbage collection. +* Improved memory usage during backup. +* Improved error handling when uploading invalid vulnerability databases. +* Improve resilience of DTR join operations. +* Hide secrets on storage config pages. + +**Deprecations** + +* The `api/v0/imagescan/layer/{layerid}` endpoint is deprecated, and will be +removed in DTR 2.5. You can use the +`/api/v0/imagescan/repositories/{namespace}/{reponame}/{tag}` endpoint instead. + + +## DTR 2.4.0 (2 November 2017) + +**New features** + +* Upgraded to Swagger 2.0 and Swagger UI 3.0. +* DTR can now be deployed on IBM Z (s390x architecture). +* Updated the `docker/dtr-rethink` images to include `rethinkcli` for easier troubleshooting. +* Notary now allows you to see audit logs using the `/v2/_trust/changefeed`, and +`/v2//_trust/changefeed` endpoints. + +**Bug fixes** + +* When setting up periodic garbage collection, it used to run in a different, +less thorough mode than when run manually. Now garbage collection always runs in +the correct mode. +* Fix error when garbage collecting manifest lists. +* Fixed issue when reconfiguring DTR from a non-local storage to NFS, causing the +change to not be persisted. +* Backported Docker Distribution race fix. [2299](https://github.com/docker/distribution/pull/2299) +* Reduced unnecessary logs in Jobrunner. +* Other general reliability improvements. + +**Known issues** + +* Backup uses too much memory and can cause out of memory issues for large databases. +* The `--nfs-storage-url` option uses the system's default NFS version instead +of testing the server to find which version works. ## Earlier versions -- [DTR 2.4 release notes](/datacenter/dtr/2.4/guides/release-notes.md) - [DTR 2.3 release notes](/datacenter/dtr/2.3/guides/release-notes.md) - [DTR 2.2 release notes](/datacenter/dtr/2.2/guides/release-notes/index.md) - [DTR 2.1 release notes](/datacenter/dtr/2.1/guides/release-notes.md)