…ncompatible (#16674)Bumps [github.com/moby/moby](https://github.com/moby/moby) from27.5.0+incompatible to 28.0.0+incompatible.<details><summary>Release notes</summary><p><em>Sourced from <ahref="https://github.com/moby/moby/releases">github.com/moby/moby'sreleases</a>.</em></p><blockquote><h2>v28.0.0</h2><h1>28.0.0</h1><p>For a full list of pull requests and changes in this release, referto the relevant GitHub milestones:</p><ul><li><ahref="https://github.com/docker/cli/issues?q=is%3Aclosed+milestone%3A28.0.0">docker/cli,28.0.0 milestone</a></li><li><ahref="https://github.com/moby/moby/issues?q=is%3Aclosed+milestone%3A28.0.0">moby/moby,28.0.0 milestone</a></li><li>Deprecated and removed features, see <ahref="https://github.com/docker/cli/blob/v28.0.0/docs/deprecated.md">DeprecatedFeatures</a>.</li><li>Changes to the Engine API, see <ahref="https://github.com/moby/moby/blob/v28.0.0/docs/api/version-history.md">APIversion history</a>.</li></ul><h2>New</h2><ul><li>Add ability to mount an image inside a container via <code>--mounttype=image</code>. <ahref="https://redirect.github.com/moby/moby/pull/48798">moby/moby#48798</a><ul><li>You can also specify <code>--mounttype=image,image-subpath=[subpath],...</code> option to mount a specificpath from the image. <ahref="https://redirect.github.com/docker/cli/pull/5755">docker/cli#5755</a></li></ul></li><li><code>docker images --tree</code> now shows metadata badges. <ahref="https://redirect.github.com/docker/cli/pull/5744">docker/cli#5744</a></li><li><code>docker load</code>, <code>docker save</code>, and <code>dockerhistory</code> now support a <code>--platform</code> flag allowing youto choose a specific platform for single-platform operations onmulti-platform images. <ahref="https://redirect.github.com/docker/cli/pull/5331">docker/cli#5331</a></li><li>Add <code>OOMScoreAdj</code> to <code>docker service create</code>and <code>docker stack</code>. <ahref="https://redirect.github.com/docker/cli/pull/5145">docker/cli#5145</a></li><li><code>docker buildx prune</code> now supports<code>reserved-space</code>, <code>max-used-space</code>,<code>min-free-space</code> and <code>keep-bytes</code> filters. <ahref="https://redirect.github.com/moby/moby/pull/48720">moby/moby#48720</a></li><li>Windows: Add support for running containerd as a child process ofthe daemon, instead of using a system-installed containerd. <ahref="https://redirect.github.com/moby/moby/pull/47955">moby/moby#47955</a></li></ul><h2>Networking</h2><ul><li>The <code>docker-proxy</code> binary has been updated, olderversions will not work with the updated <code>dockerd</code>. <ahref="https://redirect.github.com/moby/moby/pull/48132">moby/moby#48132</a><ul><li>Close a window in which the userland proxy(<code>docker-proxy</code>) could accept TCP connections, that wouldthen fail after <code>iptables</code> NAT rules were set up.</li><li>The executable <code>rootlesskit-docker-proxy</code> is no longerused, it has been removed from the build and distribution.</li></ul></li><li>DNS nameservers read from the host's <code>/etc/resolv.conf</code>are now always accessed from the host's network namespace. <ahref="https://redirect.github.com/moby/moby/pull/48290">moby/moby#48290</a><ul><li>When the host's <code>/etc/resolv.conf</code> contains nonameservers and there are no <code>--dns</code> overrides, Google's DNSservers are no longer used, apart from by the default bridge network andin build containers.</li></ul></li><li>Container interfaces in bridge and macvlan networks now use randomlygenerated MAC addresses. <ahref="https://redirect.github.com/moby/moby/pull/48808">moby/moby#48808</a><ul><li>Gratuitous ARP / Neighbour Advertisement messages will be sent whenthe interfaces are started so that, when IP addresses are reused,they're associated with the newly generated MAC address.</li><li>IPv6 addresses in the default bridge network are now IPAM-assigned,rather than being derived from the MAC address.</li></ul></li><li>The deprecated OCI <code>prestart</code> hook is now only used bybuild containers. For other containers, network interfaces are added tothe network namespace after task creation is complete, before thecontainer task is started. <ahref="https://redirect.github.com/moby/moby/pull/47406">moby/moby#47406</a></li><li>Add a new <code>gw-priority</code> option to <code>dockerrun</code>, <code>docker container create</code>, and <code>dockernetwork connect</code>. This option will be used by the Engine todetermine which network provides the default gateway for a container. On<code>docker run</code>, this option is only available through theextended <code>--network</code> syntax. <ahref="https://redirect.github.com/docker/cli/pull/5664">docker/cli#5664</a></li><li>Add a new netlabel <code>com.docker.network.endpoint.ifname</code>to customize the interface name used when connecting a container to anetwork. It's supported by all built-in network drivers on Linux. <ahref="https://redirect.github.com/moby/moby/pull/49155">moby/moby#49155</a><ul><li>When a container is created with multiple networks specified,there's no guarantee on the order networks will be connected to thecontainer. So, if a custom interface name uses the same prefix as theauto-generated names, for example <code>eth</code>, the container mightfail to start.</li><li>The recommended practice is to use a different prefix, for example<code>en0</code>, or a numerical suffix high enough to never collide,for example <code>eth100</code>.</li><li>This label can be specified on <code>docker network connect</code>via the <code>--driver-opt</code> flag, for example <code>docker networkconnect --driver-opt=com.docker.network.endpoint.ifname=foobar…</code>.</li><li>Or via the long-form <code>--network</code> flag on <code>dockerrun</code>, for example <code>docker run--network=name=bridge,driver-opt=com.docker.network.endpoint.ifname=foobar…</code></li></ul></li><li>If a custom network driver reports capability<code>GwAllocChecker</code> then, before a network is created, it willget a <code>GwAllocCheckerRequest</code> with the network's options. Thecustom driver may then reply that no gateway IP address should beallocated. <ahref="https://redirect.github.com/moby/moby/pull/49372">moby/moby#49372</a></li></ul><h2>Port publishing in bridge networks</h2><ul><li><code>dockerd</code> now requires <code>ipset</code> support in theLinux kernel. <ahref="https://redirect.github.com/moby/moby/pull/48596">moby/moby#48596</a><ul><li>The <code>iptables</code> and <code>ip6tables</code> rules used toimplement port publishing and network isolation have been extensivelymodified. This enables some of the following functional changes, and isa first step in refactoring to enable native <code>nftables</code>support in a future release. <ahref="https://redirect.github.com/moby/moby/issues/48815">moby/moby#48815</a></li><li>If it becomes necessary to downgrade to an earlier version of thedaemon, some manual cleanup of the new rules will be necessary. Thesimplest and surest approach is to reboot the host, or use<code>iptables -F</code> and <code>ip6tables -F</code> to flush allexisting <code>iptables</code> rules from the <code>filter</code> tablebefore starting the older version of the daemon. When that is notpossible, run the following commands as root:<ul><li><code>iptables -D FORWARD -m set --match-set docker-ext-bridges-v4dst -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT; ip6tables -DFORWARD -m set --match-set docker-ext-bridges-v6 dst -m conntrack--ctstate RELATED,ESTABLISHED -j ACCEPT</code></li><li><code>iptables -D FORWARD -m set --match-set docker-ext-bridges-v4dst -j DOCKER; ip6tables -D FORWARD -m set --match-setdocker-ext-bridges-v6 dst -j DOCKER</code></li><li>If you were previously running with the iptables filter-FORWARDpolicy set to <code>ACCEPT</code> and need to restore access tounpublished ports, also delete per-bridge-network rules from the<code>DOCKER</code> chains. For example, <code>iptables -D DOCKER ! -idocker0 -o docker0 -j DROP</code>.</li></ul></li></ul></li><li>Fix a security issue that was allowing remote hosts to connectdirectly to a container on its published ports. <ahref="https://redirect.github.com/moby/moby/pull/49325">moby/moby#49325</a></li><li>Fix a security issue that was allowing neighbor hosts to connect toports mapped on a loopback address. <ahref="https://redirect.github.com/moby/moby/pull/49325">moby/moby#49325</a></li></ul><!-- raw HTML omitted --></blockquote><p>... (truncated)</p></details><details><summary>Commits</summary><ul><li><ahref="https://github.com/moby/moby/commit/af898abe44662d9554fb15ee4d4a7307f1b8e315"><code>af898ab</code></a>Merge pull request <ahref="https://redirect.github.com/moby/moby/issues/49495">#49495</a>from vvoland/update-buildkit</li><li><ahref="https://github.com/moby/moby/commit/d67f035d31bab71be3ae7dcaacba41f5a98aad11"><code>d67f035</code></a>vendor: github.com/moby/buildkit v0.20.0</li><li><ahref="https://github.com/moby/moby/commit/00ab386b5a2ebcf85b6a03b800f593c3a140c6a8"><code>00ab386</code></a>Merge pull request <ahref="https://redirect.github.com/moby/moby/issues/49491">#49491</a>from vvoland/update-buildkit</li><li><ahref="https://github.com/moby/moby/commit/1fde8c46159cb41f584c01551f83cc21ecf924d9"><code>1fde8c4</code></a>builder-next: fix cdi manager</li><li><ahref="https://github.com/moby/moby/commit/cde9f0752e9c9f63b459e0247ff7df0b35488af3"><code>cde9f07</code></a>vendor: github.com/moby/buildkit v0.20.0-rc3</li><li><ahref="https://github.com/moby/moby/commit/89e1429b65f194b25fe2e31088a4c4e69a651a47"><code>89e1429</code></a>Merge pull request <ahref="https://redirect.github.com/moby/moby/issues/49490">#49490</a>from thaJeztah/dockerfile_linting</li><li><ahref="https://github.com/moby/moby/commit/b2b55903d0bb54e11bfe22204c1e0b73627943eb"><code>b2b5590</code></a>Dockerfile: fix linting warnings</li><li><ahref="https://github.com/moby/moby/commit/62bc5979908f152a8929ce44927cbdd929bf53ea"><code>62bc597</code></a>Merge pull request <ahref="https://redirect.github.com/moby/moby/issues/49480">#49480</a>from thaJeztah/docs_api_1.48</li><li><ahref="https://github.com/moby/moby/commit/670cd81423932b3e9103f0893c5d5e63a079ae58"><code>670cd81</code></a>Merge pull request <ahref="https://redirect.github.com/moby/moby/issues/49485">#49485</a>from vvoland/c8d-list-panic</li><li><ahref="https://github.com/moby/moby/commit/a3628f3f8e806ede250e2c95f6757070c9fb56e4"><code>a3628f3</code></a>docs/api: add documentation for API v1.48</li><li>Additional commits viewable in <ahref="https://github.com/moby/moby/compare/v27.5.0...v28.0.0">compareview</a></li></ul></details><br />[![Dependabot compatibilityscore](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/moby/moby&package-manager=go_modules&previous-version=27.5.0+incompatible&new-version=28.0.0+incompatible)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)Dependabot will resolve any conflicts with this PR as long as you don'talter it yourself. You can also trigger a rebase manually by commenting`@dependabot rebase`.[//]: # (dependabot-automerge-start)[//]: # (dependabot-automerge-end)---<details><summary>Dependabot commands and options</summary><br />You can trigger Dependabot actions by commenting on this PR:- `@dependabot rebase` will rebase this PR- `@dependabot recreate` will recreate this PR, overwriting any editsthat 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 afteryour CI passes on it- `@dependabot cancel merge` will cancel a previously requested mergeand block automerging- `@dependabot reopen` will reopen this PR if it is closed- `@dependabot close` will close this PR and stop Dependabot recreatingit. You can achieve the same result by closing it manually- `@dependabot show <dependency name> ignore conditions` will show allof the ignore conditions of the specified dependency- `@dependabot ignore this major version` will close this PR and stopDependabot creating any more for this major version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this minor version` will close this PR and stopDependabot creating any more for this minor version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this dependency` will close this PR and stopDependabot creating any more for this dependency (unless you reopen thePR or upgrade to it yourself)</details>Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>