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

[dependabot]

Bumps github.com/docker/docker from 26.0.0+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:

• docker/cli, 26.1.3 milestone
• moby/moby, 26.1.3 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

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:

• docker/cli, 26.1.2 milestone
• moby/moby, 26.1.2 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

Bug fixes and enhancements

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

Packaging updates

• Update Go runtime to 1.21.10. moby/moby#47806

v26.1.1

26.1.1

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

• docker/cli, 26.1.1 milestone
• moby/moby, 26.1.1 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

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

• 8e96db1 Merge pull request #47832 from vvoland/v26.1-47821
• c21fe3e Forward DNS requests into --internal networks
• 86af4ed Merge pull request #47833 from vvoland/v26.1-47744
• 73511cd Merge pull request #47829 from vvoland/v26.1-47749
• 9326cda Do not forward DNS requests to self.
• 76fcf9a apparmor: Allow confined runc to kill containers
• ef1912d Merge pull request #47806 from vvoland/v26.1-47805
• 10739af update to go1.21.10
• ac2de55 Merge pull request #47775 from vvoland/v26.1-47771
• 9a2b531 Merge pull request #47774 from vvoland/v26.1-47769
• 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 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)

[github-actions]

Temporary image deleted.

[zapier-sre-bot]

Mergecat's Review

Click to read mergecats review!

😼 Mergecat review of go.mod

@@ -10,7 +10,7 @@ require (
 	github.com/cenkalti/backoff/v4 v4.3.0
 	github.com/chainguard-dev/git-urls v1.0.2
 	github.com/creasty/defaults v1.7.0
-	github.com/docker/docker v26.0.2+incompatible
+	github.com/docker/docker v26.1.3+incompatible
 	github.com/ghodss/yaml v1.0.0
 	github.com/go-git/go-git-fixtures/v4 v4.3.2-0.20231010084843-55a94097c399
 	github.com/go-logr/zerologr v1.2.3

Feedback & Suggestions:

1. Dependency Update Verification: Ensure that the new version v26.1.3+incompatible of github.com/docker/docker is compatible with your project. Check the release notes and changelog for any breaking changes or important updates that might affect your codebase.

2. Testing: After updating the dependency, run your test suite to verify that everything works as expected. This helps catch any issues introduced by the new version early.

3. Locking Dependencies: Consider using a tool like go mod tidy to clean up your go.mod file and ensure that all dependencies are properly locked. This can help avoid issues with transitive dependencies.

4. Security Review: Review the security advisories for the new version of github.com/docker/docker to ensure there are no known vulnerabilities that could affect your project.

---

---

Dependency Review

Click to read mergecats review!

No suggestions found

[zapier-sre-bot]

Mergecat's Review

Click to read mergecats review!

😼 Mergecat review of go.mod

@@ -10,7 +10,7 @@ require (
 	github.com/cenkalti/backoff/v4 v4.3.0
 	github.com/chainguard-dev/git-urls v1.0.2
 	github.com/creasty/defaults v1.7.0
-	github.com/docker/docker v26.0.2+incompatible
+	github.com/docker/docker v26.1.3+incompatible
 	github.com/ghodss/yaml v1.0.0
 	github.com/go-git/go-git-fixtures/v4 v4.3.2-0.20231010084843-55a94097c399
 	github.com/go-logr/zerologr v1.2.3

Feedback & Suggestions:

1. Dependency Update Verification: Ensure that the new version v26.1.3+incompatible of github.com/docker/docker is compatible with your project. Check the release notes and changelog for any breaking changes or important updates that might affect your codebase.

2. Testing: After updating the dependency, run your test suite to verify that everything works as expected. This will help catch any issues introduced by the new version.

3. Security Review: Review the security advisories for the new version to ensure there are no known vulnerabilities. This is especially important for dependencies like docker that can have significant security implications.

4. Lock File Update: If you are using a lock file (e.g., go.sum), make sure to update it accordingly to reflect the new dependency version. This ensures consistency across different environments.

---

---

Dependency Review

Click to read mergecats review!

No suggestions found

[dependabot]

Superseded by #230.