flyteorg
Bump github.com/docker/docker from 20.10.7+incompatible to 24.0.9+incompatible in /flytectl
Bumps github.com/docker/docker from 20.10.7+incompatible to 24.0.9+incompatible.
Release notes
Sourced from github.com/docker/docker's releases.
v24.0.9
24.0.9
For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:
Security
This release contains security fixes for the following CVEs affecting Docker Engine and its components.
CVE Component Fix version Severity CVE-2024-21626 runc 1.1.12 High, CVSS 8.6 CVE-2024-24557 Docker Engine 24.0.9 Medium, CVSS 6.9 Important ⚠️
Note that this release of Docker Engine doesn't include fixes for the following known vulnerabilities in BuildKit:
To address these vulnerabilities, upgrade to Docker Engine v25.0.2.
For more information about the security issues addressed in this release, and the unaddressed vulnerabilities in BuildKit, refer to the blog post. For details about each vulnerability, see the relevant security advisory:
Packaging updates
- Upgrade runc to v1.1.12. moby/moby#47269
- Upgrade containerd to v1.7.13 (static binaries only). moby/moby#47280
v24.0.8
24.0.8
For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:
Bug fixes and enhancements
- Live restore: Containers with auto remove (
docker run --rm) are no longer forcibly removed on engine restart. moby/moby#46857
... (truncated)
Commits
fca702dMerge pull request from GHSA-xw73-rw38-6vjcf78a772Merge pull request #47281 from thaJeztah/24.0_backport_bump_containerd_binary...61afffeMerge pull request #47270 from thaJeztah/24.0_backport_bump_runc_binary_1.1.12b38e74cMerge pull request #47276 from thaJeztah/24.0_backport_bump_runc_1.1.12dac5663update containerd binary to v1.7.1320e1af3vendor: github.com/opencontainers/runc v1.1.12858919dupdate runc binary to v1.1.12141ad39Merge pull request #47266 from vvoland/ci-fix-makeps1-templatefail-24db968c6hack/make.ps1: Fix go list pattern61c51fbMerge pull request #47221 from vvoland/pkg-pools-close-noop-24- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
@eapolinario if you could merge this one that would be great - thanks! It includes a number of CVE resolutions.
Sorry, only users with push access can use that command.
Ah well, I tried!
@ddl-ebrown , jumping 4 major versions of docker brought in some incompatibilities. We'll need to invest time in updating the code to use the new docker API. Do you want to take a crack at it?
@eapolinario I should be able to take care of that.
How will the binary ship now that it's in the monorepo?
@eapolinario I should be able to take care of that.
Thank you!
How will the binary ship now that it's in the monorepo? I'm working on a change to enable us to ship flytectl from the monorepo using goreleaser. It'll be a workflow we run manually in the beginning. Once that change is out I'm going to archive the flytectl repo.
Can be closed in favor of #5363 which fixes the compilation @eapolinario. Thanks!
Looks like github.com/docker/docker is up-to-date now, so this is no longer needed.