kernel-module-management icon indicating copy to clipboard operation
kernel-module-management copied to clipboard

Bump github.com/docker/docker from 26.0.1+incompatible to 26.1.3+incompatible

Open dependabot[bot] opened this issue 1 year ago • 3 comments

Bumps github.com/docker/docker from 26.0.1+incompatible to 26.1.3+incompatible.

Release notes

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

v26.1.3

26.1.3

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

Bug fixes and enhancements

  • Fix a regression that prevented the use of DNS servers within a --internal network. moby/moby#47832
  • When the internal DNS server's own address is supplied as an external server address, ignore it to avoid unproductive recursion. moby/moby#47833

Packaging updates

  • Allow runc to kill containers when confined to the runc profile in AppArmor version 4.0.0 and later. moby/moby#47829

v26.1.2

26.1.2

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

Bug fixes and enhancements

  • Fix issue where the CLI process would sometimes hang when a container failed to start. docker/cli#5062

Packaging updates

v26.1.1

26.1.1

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

Bug fixes and enhancements

  • Fix docker run -d printing an context canceled spurious error when OTEL is configured. docker/cli#5044
  • Experimental environment variable DOCKER_BRIDGE_PRESERVE_KERNEL_LL=1 will prevent the daemon from removing the kernel-assigned link local address on a Linux bridge. moby/moby#47775
  • Resolve an issue preventing container creation on hosts with a read-only /proc/sys/net filesystem. If IPv6 cannot be disabled on an interface due to this, either disable IPv6 by default on the host or ensure /proc/sys/net is read-write. Otherwise, start dockerd with DOCKER_ALLOW_IPV6_ON_IPV4_INTERFACE=1 to bypass the error. moby/moby#47769

[!NOTE]

... (truncated)

Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

dependabot[bot] avatar May 16 '24 18:05 dependabot[bot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a rh-ecosystem-edge member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci[bot] avatar May 16 '24 18:05 openshift-ci[bot]

Deploy Preview for openshift-kmm ready!

Name Link
Latest commit 3c2dc80e7d5e2f336790e013a3fa2bc57034ae8d
Latest deploy log https://app.netlify.com/sites/openshift-kmm/deploys/6654696c42c5530008d2f704
Deploy Preview https://deploy-preview-1116--openshift-kmm.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

netlify[bot] avatar May 16 '24 18:05 netlify[bot]

/ok-to-test

yevgeny-shnaidman avatar May 23 '24 09:05 yevgeny-shnaidman

/lgtm /assign @ybettan

yevgeny-shnaidman avatar May 23 '24 09:05 yevgeny-shnaidman

/approve

ybettan avatar May 27 '24 10:05 ybettan

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], ybettan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci[bot] avatar May 27 '24 10:05 openshift-ci[bot]

/lgtm

qbarrand avatar May 27 '24 12:05 qbarrand