cloudfoundry / guardian

containers4life
Apache License 2.0
77 stars 44 forks source link

Bump github.com/docker/docker from 24.0.1+incompatible to 24.0.2+incompatible #399

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/docker/docker from 24.0.1+incompatible to 24.0.2+incompatible.

Release notes

Sourced from github.com/docker/docker's releases.

v24.0.2

24.0.2

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

Bug fixes and enhancements

  • Fix a panic during build when referencing locally tagged images. moby/buildkit#3899, moby/moby#45582
  • Fix builds potentially failing with exit code: 4294967295 when performing many concurrent build stages. moby/moby#45620
  • Fix DNS resolution on Windows ignoring etc/hosts (%WINDIR%\System32\Drivers\etc\hosts), including resolution of localhost. moby/moby#45562
  • Apply a workaround for a containerd bug that causes concurrent docker exec commands to take significantly longer than expected. moby/moby#45625
  • containerd image store: Fix an issue where the image Created field would contain an incorrect value. moby/moby#45623
  • containerd image store: Adjust the output of image pull progress so that the output has the same format regardless of whether the containerd image store is enabled. moby/moby#45602
  • containerd image store: Switching between the default and containerd image store now requires a daemon restart. moby/moby#45616
Commits
  • 659604f Merge pull request #45625 from thaJeztah/24.0_backport_serialize_exec_starts_...
  • 6660133 Merge pull request #45582 from thaJeztah/24.0_backport_vendor_buildkit_0.11.7...
  • 67b3563 Merge pull request #45623 from vvoland/c8d-inspect-created-time-24
  • 7a4ea19 libcontainerd: work around exec start bug in c8d
  • ae6e933 vendor: github.com/moby/buildkit v0.11.7-0.20230525183624-798ad6b0ce9f
  • 0d9acd2 c8d/inspect: Fill Created time if available
  • 37bc639 Merge pull request #45620 from thaJeztah/24.0_backport_update_go_runc_v1.1.0
  • 04eccf8 vendor: github.com/containerd/go-runc v1.1.0
  • 2472277 Merge pull request #45616 from thaJeztah/24.0_backport_lock_in_snapshotter_se...
  • 9d8acb7 Merge pull request #45612 from vvoland/dangling-image-repotagsdigests-test-24
  • Additional commits viewable in compare view


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
cf-gitbot commented 1 year ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

dependabot[bot] commented 1 year ago

Looks like github.com/docker/docker is up-to-date now, so this is no longer needed.