🌱 Bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible in /test #1780

dependabot · 2024-06-17T20:07:07Z

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

metal3-io-bot · 2024-06-17T20:07:15Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign adilghaffardev for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

OWNERS

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

metal3-io-bot · 2024-06-17T20:07:19Z

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

I'm waiting for a metal3-io 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/test-infra repository.

tuminoid · 2024-06-18T05:10:53Z

/ok-to-test
/retest

tuminoid · 2024-06-18T05:13:51Z

Hmm, whats up with golangci-lint? Does not look like Docker bump issue... @kashifest

https://github.com/metal3-io/cluster-api-provider-metal3/actions/runs/9554048035/job/26349548409?pr=1780

run golangci-lint
  Running [/home/runner/golangci-lint-1.56.2-linux-amd64/golangci-lint run --path-prefix=test] in [/home/runner/work/cluster-api-provider-metal3/cluster-api-provider-metal3/test] ...
  Received 1288363 of 1288363 (100.0%), 1.2 MBs/sec
  level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package container: could not load export data: no export data for \"sigs.k8s.io/cluster-api/test/infrastructure/container\""
  level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package container: could not load export data: no export data for \"sigs.k8s.io/cluster-api/test/infrastructure/container\""

tuminoid · 2024-06-18T05:17:22Z

/retest

Hmm, whats up with golangci-lint? Does not look like Docker bump issue... @kashifest

https://github.com/metal3-io/cluster-api-provider-metal3/actions/runs/9554048035/job/26349548409?pr=1780

run golangci-lint
  Running [/home/runner/golangci-lint-1.56.2-linux-amd64/golangci-lint run --path-prefix=test] in [/home/runner/work/cluster-api-provider-metal3/cluster-api-provider-metal3/test] ...
  Received 1288363 of 1288363 (100.0%), 1.2 MBs/sec
  level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package container: could not load export data: no export data for \"sigs.k8s.io/cluster-api/test/infrastructure/container\""
  level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package container: could not load export data: no export data for \"sigs.k8s.io/cluster-api/test/infrastructure/container\""

OK, build fails as well. There is incompatibility with CAPI 1.7.3 here, hence failing.

# sigs.k8s.io/cluster-api/test/infrastructure/container
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/infrastructure/container/docker.go:121:62: undefined: types.ImagePullOptions
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/infrastructure/container/docker.go:140:53: undefined: types.ImageListOptions

/hold
Needs CAPI 1.8

tuminoid · 2024-06-18T05:20:46Z

/retest

Bumps [github.com/docker/docker](https://github.com/docker/docker) from 26.1.4+incompatible to 27.0.0+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](https://github.com/docker/docker/commits) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

metal3-io-bot · 2024-06-18T09:07:25Z

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
build	`356ef22`	link	true	`/test build`

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

kashifest · 2024-06-26T05:38:50Z

This version of docker client had issues while releasing in upstream, check this comment, I noticed it yesterday and pushed a bump in CAPI upstream, kubernetes-sigs/cluster-api#10794, dependabot should pick it up soon, or then I will bump it as part of #1805

dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jun 17, 2024

metal3-io-bot requested review from kashifest and Rozzii June 17, 2024 20:07

metal3-io-bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 17, 2024

metal3-io-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 17, 2024

metal3-io-bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 18, 2024

metal3-io-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 18, 2024

dependabot bot force-pushed the dependabot/go_modules/test/main/github.com/docker/docker-27.0.0incompatible branch from cf0b949 to 356ef22 Compare June 18, 2024 09:03

Rozzii added this to the 1.8.0 milestone Jun 28, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🌱 Bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible in /test #1780

🌱 Bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible in /test #1780

dependabot bot commented on behalf of github Jun 17, 2024 •

edited

Loading

metal3-io-bot commented Jun 17, 2024

metal3-io-bot commented Jun 17, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

metal3-io-bot commented Jun 18, 2024

kashifest commented Jun 26, 2024

🌱 Bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible in /test #1780

Are you sure you want to change the base?

🌱 Bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible in /test #1780

Conversation

dependabot bot commented on behalf of github Jun 17, 2024 • edited Loading

v27.0.0-rc.2

27.0.0-rc.2

New

Bug fixes and enhancements

Removed

API

Packaging updates

v27.0.0-rc.1

27.0.0-rc.1

metal3-io-bot commented Jun 17, 2024

metal3-io-bot commented Jun 17, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

tuminoid commented Jun 18, 2024

metal3-io-bot commented Jun 18, 2024

kashifest commented Jun 26, 2024

dependabot bot commented on behalf of github Jun 17, 2024 •

edited

Loading