Bump github.com/docker/docker from 26.0.2+incompatible to 27.0.0+incompatible

[dependabot]

Bumps github.com/docker/docker from 26.0.2+incompatible to 27.0.0+incompatible.

Release notes

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

v27.0.0-rc.2

27.0.0-rc.2

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

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

New

• In port mappings with no host port specified, and with host port ranges, allocate the same port for IPv4 and IPv6. Add bridge driver option com.docker.network.bridge.gateway_mode_ipv6=<nat|routed>, when set to routed no NAT or masquerading rules are configured for port mappings. This enables direct IPv6 access to the container, if the host's network can route packets for the container's address to the host. Mapped ports will be opened in the containers firewall. For example, docker network create --ipv6 -o com.docker.network.bridge.gateway_mode_ipv6=routed mynet. Option com.docker.network.bridge.gateway_mode_ipv4=<nat|routed> is also available. moby/moby#47871

Bug fixes and enhancements

• Fix a goroutine and file-descriptor leak on container attach. moby/moby#45052
• Clear the networking state of all stopped or dead containers during daemon start-up. moby/moby#47984
• Environment variable DOCKER_ALLOW_IPV6_ON_IPV4_INTERFACE, introduced in release 26.1.1, no longer has any effect. If IPv6 could not be disabled on an interface because of a read-only /proc/sys/net, the environment variable allowed the container to start anyway. IPv6 can now be explicitly enabled simply by using --ipv6 when creating the network, it is no longer necessary to allocate a subnet as a unique-local prefix will be selected by default. Other workarounds are to configure the OS to disable IPv6 by default on new interfaces, mount /proc/sys/net read-write, or use a kernel with no IPv6 support. moby/moby#47963

Removed

• pkg/archive: deprecate NewTempArchive, TempArchive. These types were only used in tests and will be removed in the next release. moby/moby#48002
• pkg/archive: deprecate CanonicalTarNameForPath moby/moby#48001
• Deprecate pkg/dmesg. This package was no longer used, and will be removed in the next release. moby/moby#47999
• Deprecate pkg/stringid.ValidateID and pkg/stringid.IsShortID moby/moby#47995
• runconfig: deprecate SetDefaultNetModeIfBlank and move ContainerConfigWrapper to api/types/container moby/moby#48007

API

• POST /containers/create and POST /services/create now take Options as part of HostConfig.Mounts.TmpfsOptions allowing to set options for tmpfs mounts. moby/moby#46809
• The Healthcheck.StartInterval property is now correctly ignored when updating a Swarm service using API versions less than v1.44. moby/moby#47991
• GET /events now supports image create event that is emitted when a new image is built regardless if it was tagged or not. moby/moby#47929
• GET /info now includes a Containerd field containing information about the location of the containerd API socket and containerd namespaces used by the daemon to run containers and plugins. moby/moby#47239

Packaging updates

• Update runc to v1.1.13 moby/moby#47976

v27.0.0-rc.1

27.0.0-rc.1

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

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

... (truncated)

Commits

• See full diff 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)

[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 v27.0.0+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. Compatibility Check: Ensure that the new version v27.0.0 of github.com/docker/docker is compatible with your existing codebase. Major version changes can introduce breaking changes. Review the release notes and migration guides provided by the library.

2. Testing: After updating the dependency, run your test suite to verify that everything works as expected. Pay special attention to any integration tests that involve Docker.

3. Locking Versions: If you encounter any issues with the new version, consider using a more specific version or a patch version if available. This can help avoid unexpected issues from future updates.

4. Security Review: Check for any security advisories related to the new version. Ensure that the update does not introduce any known vulnerabilities.

5. Documentation: Update any internal documentation that references the version of github.com/docker/docker being used, if applicable.

---

---

Dependency Review

Click to read mergecats review!

No suggestions found

[github-actions]

Temporary image deleted.

[dependabot]

Superseded by #236.