Skip to content

engine: add release notes for 20.10.16 #14709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thaJeztah merged 1 commit into from
May 18, 2022
Merged

engine: add release notes for 20.10.16 #14709

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 29 additions & 4 deletions engine/release-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,34 @@ for Docker Engine.

# Version 20.10

## 20.10.16
2022-05-12

This release of Docker Engine fixes a regression in the Docker CLI builds for
Copy link
Contributor

@dockertopia dockertopia May 12, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get the idea of doing a quick summary at the top, especially for a scenario of a "what's new" and dealing with new features, but this is a short list of items and info is repeated and close by below this paragraph. Just wondering if it is necessary.

Copy link
Member Author

@thaJeztah thaJeztah May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, tried to stick with the format we used. I agree that for shorter change logs it's a bit redundant (although the summary can sometimes be written slightly more, well, as a summary, without the nitty-gritty details if people don't need them).

macOS, fixes an issue with `docker stats` when using containerd 1.5 and up,
and updates the Go runtime to include a fix for [CVE-2022-29526](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}.

### Client

- Fixed a regression in binaries for macOS introduced in [20.10.15](#201015), which
resulted in a panic [docker/cli#43426](https://github.com/docker/cli/pull/3592){:target="_blank" rel="noopener"}.
Copy link
Contributor

@dockertopia dockertopia May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
resulted in a panic [docker/cli#43426](https://github.com/docker/cli/pull/3592){:target="_blank" rel="noopener"}.
resulted in a panic [docker/cli #43426](https://github.com/docker/cli/pull/3592){:target="_blank" rel="noopener"}.

Copy link
Contributor

@dockertopia dockertopia May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it becomes more readable with a space between repo and issue nr.

Copy link
Member Author

@thaJeztah thaJeztah May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we used this format for all change-logs, and we picked this format to match the format that GitHub itself uses.

if we decide to change, we should probably do it across the board (probably better to do that separately).

I will have to check if that could cause potential issues; GitHub can be very "eager" to try to link together issues/pull requests, which means that including certain strings in a text sometimes causes those to show up as "linked commit" on those tickets/PR's (and in some cases even send out e-mails to all participants on them).

Copy link
Contributor

@dockertopia dockertopia May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this be an issue for others release notes? Like I mentioned earlier there is a discussion in its very early stages about normalizing release notes across manuals. This would involve some details like mentioning dates of releases (with parenthesis in some places, without in others, past tenses used, how issue numbers are presented... individually small things, all together making pages look different).

Copy link
Member Author

@thaJeztah thaJeztah May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

w.r.t. changing the format of the dates, we may have to be careful, as doing so might break the anchor-links (so we'd have to replace them with custom anchors)

But yes, if we have ideas on improving the release notes, we should try to match (where possible); probably do so all at once?

Copy link
Contributor

@dockertopia dockertopia May 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, better check first the changes we want to make across RN and then check if they have impact.

- Update golang.org/x/sys dependency which contains a fix for
[CVE-2022-29526](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}.

### Daemon

- Fixed an issue where `docker stats` was showing empty stats when running with
containerd 1.5.0 or up [moby/moby#43567](https://github.com/moby/moby/pull/43567){:target="_blank" rel="noopener"}.
- Updated the `golang.org/x/sys` build-time dependency which contains a fix for [CVE-2022-29526](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}.

### Packaging

- Updated Go runtime to [1.17.10](https://go.dev/doc/devel/release#go1.17.minor){:target="_blank" rel="noopener"},
which contains a fix for [CVE-2022-29526](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}.
- Used "weak" dependencies for the `docker scan` CLI plugin, to prevent a
"conflicting requests" error when users performed an off-line installation from
downloaded RPM packages [docker/docker-ce-packaging#659](https://github.com/docker/docker-ce-packaging/pull/659){:target="_blank" rel="noopener"}.

## 20.10.15
2022-05-05

Expand All @@ -32,10 +60,7 @@ This release of Docker Engine comes with updated versions of the `compose`,
> **Known issues**
>
> We've identified an issue with the [macOS CLI binaries](https://download.docker.com/mac/static/stable/){:target="_blank" rel="noopener" class="_"}
> in the 20.10.15 release. A [fix for this issue](https://github.com/docker/cli/pull/3592){:target="_blank" rel="noopener" class="_"}
> has been merged and will be included in the next patch release (20.10.16). In
> the meantime, we recommend using the 20.10.14 binaries for macOS instead. Other
> platforms are not affected.
> in the 20.10.15 release. This issue has been resolved in the [20.10.16](#201016) release.
{:.important}

### Daemon
Expand Down