Skip to content
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.

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

[202012] Update dockerd and containerd versions #10856

Draft
wants to merge 2 commits into
base: 202012
Choose a base branch
from

Conversation

vaibhavhd
Copy link
Contributor

@vaibhavhd vaibhavhd commented May 17, 2022

Why I did it

dockerd version in 202012 branch is old, and is missing critical fixes and resolved CVEs.

Examples of missing fixes that have already impacted in older branches:

moby/moby#41586
moby/moby#41588

How I did it

Update DOCKER_VERSION from 5:18.09.8~3-0~debian to 5:20.10.16~3-0~debian-buster
And set CONTAINERD_IO_VERSION to 1.6.4-1

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

build_debian.sh Outdated
@@ -31,7 +31,8 @@ set -x -e
CONFIGURED_ARCH=$([ -f .arch ] && cat .arch || echo amd64)

## docker engine version (with platform)
DOCKER_VERSION=5:18.09.8~3-0~debian-$IMAGE_DISTRO
DOCKER_VERSION=5:20.10.8~3-0~debian-$IMAGE_DISTRO
Copy link
Contributor

Choose a reason for hiding this comment

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

Any particular reason for 20.10.8? We have 20.10.14 in master currently, with 20.10.15 being the latest.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was unintentional. I picked the last listed version in official package list for buster. Did not realize that the list wasn't naturally sorted.
Fixed now to latest - 20.10.16

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also, ideally if we take this change to 202012, then even master branch should be updated with this. I think master shouldn't be behind 202012 in any case.

@vaibhavhd
Copy link
Contributor Author

/Azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@vaibhavhd
Copy link
Contributor Author

/Azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vaibhavhd
Copy link
Contributor Author

/Azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants