Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github.com/docker/docker from 26.1.4+incompatible to 27.0.0+incompatible #16

Conversation

dependabot[bot]
Copy link
Contributor

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

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.1

27.0.0-rc.1

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

New

  • Add support to docker stack deploy for driver_opts in a service's networks. docker/cli#5125
  • containerd image store: Add --platform flag to docker image push and improve the default behavior when not all platforms of the multi-platform image are available locally. docker/cli#4984, moby/moby#47679

Bug fixes and enhancements

  • Fix a bug causing the docker CLI to leak UNIX sockets in $TMPDIR in some cases. docker/cli#5146
  • Don't ignore a custom seccomp profile when used in conjunction with --privileged moby/moby#47500
  • rootless: overlay2: support native overlay diff when using rootless-mode in kernel 5.11 and above moby/moby#47605
  • Fix the StartInterval default value of healthcheck to reflect the documented value of 5s. moby/moby#47799
  • Allow sysctls to be set per-interface during container creation and network connection. moby/moby#47686
  • A ULA base prefix is automatically added to default-address-pools if this parameter wasn't manually configured, or if it contains no IPv6 prefixes. This ULA prefix is derived from the Engine host ID such that it's unique across hosts and over time. moby/moby#47853
  • Enable ip6tables by default, it is no longer --experimental. moby/moby#47747
  • Introduce a new subnet allocator that can deal with IPv6 address pools of any size moby/moby#47768
  • For IPv6-enabled bridge networks, do not attempt to replace the bridge's kernel-assigned link local address with fe80::1. moby/moby#47787
  • Fix docker save and docker load not ending on the daemon side when the operation was cancelled (eg. Ctrl+C) moby/moby#47629
  • Container's StartedAt property is now recorded before container startup, guaranteeing that the StartedAt is always before FinishedAt. moby/moby#47003
  • Run an internal resolver on the default bridge network to forward DNS requests to external resolvers, even if they are on localhost addresses, or IPv6 addresses when the default bridge does not have IPv6 connectivity. To preserve existing behavior, the internal resolver on the default bridge will not resolve container names, unlike the resolver on user-defined networks. Do not use Google's DNS servers as a fallback when no external DNS servers are supplied in configuration via --dns or available from the host's resolv.conf. moby/moby#47602
  • If firewalld is running on the host, create policy docker-forwarding to allow forwarding from any zone to the docker zone. This makes it possible to configure a bridge network with a routable IPv6 address, and no masquerading. moby/moby#47745
  • IPv6 can now be enabled by default on all custom networks using dockerd --default-network-opt=bridge=com.docker.network.enable_ipv6=true (and the matching json option). moby/moby#47867
  • The internal DNS resolver used by Windows containers on Windows will now forward requests to external DNS servers by-default, this enables nslookup to resolve external hostnames. This behaviour can be disabled via daemon.json, using "features": { "windows-dns-proxy": false }, the feature flag will be removed in a future release. moby/moby#47826
  • Document the use of driver-opt in the CLI for setting per-interface sysctls. docker/cli#4994
  • Print a warning when the CLI does not have permissions to read the configuration file. docker/cli#5077

API

  • containerd image store: POST /images/{name}/push now supports a platform parameter (JSON encoded OCI Platform type) that allows selecting a specific platform-manifest from the multi-platform image. This is experimental and may change in future API versions. moby/moby#47679
  • ContainerList api returns container annotations. moby/moby#47866
  • Deprecate the daemon flag --api-cors-header and the corresponding daemon.json config param. These will be removed in the next major release. moby/moby#45313
  • Client API callback functions client.RequestPrivilegeFunc, client.ImageSearchOptions.AcceptPermissionsFunc and image.ImportOptions.PrivilegeFunc now require a context parameter. moby/moby#47536
  • Remove deprecated ImageImportOptions, ImageCreateOptions, ImagePullOptions, ImagePushOptions, ImageListOptions, ImageRemoveOptions aliases for Image types. moby/moby#47900
  • Move ExecConfig, ContainerExecInspect, ContainersPruneReport, ContainerPathStat, CopyToContainerOptions, ExecStartCheck and ContainerStats to api/types/container; ImagesPruneReport, ImageImportSource and ImageLoadResponse to api/types/image; ExecStartOptions to api/types/backend; VolumesPruneReport to api/types/volume; EventsOptions to api/types/events; ImageSearchOptions to api/types/registry. moby/moby#47936
  • Deprecate non-standard (config) fields in image inspect output. The Config field returned by this endpoint (used for "image inspect") returned additional fields that are not part of the image's configuration and not part of the [Docker Image Spec] and the [OCI Image Spec]. These fields are never set (and always return the default value for the type), but are not omitted in the response when left empty. As these fields were not intended to be part of the image configuration response, they are deprecated, and will be removed in the future API versions. The following fields are currently included in the API response, but are not part of the underlying image's Config, and deprecated:
    • Hostname

... (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)

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]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jun 17, 2024
Copy link

coderabbitai bot commented Jun 17, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 28, 2024

Superseded by #18.

@dependabot dependabot bot closed this Jun 28, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/docker/docker-27.0.0incompatible branch June 28, 2024 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants