diff --git a/content/engine/release-notes/25.0.md b/content/engine/release-notes/25.0.md index 3d764e12eb..221a3eed1d 100644 --- a/content/engine/release-notes/25.0.md +++ b/content/engine/release-notes/25.0.md @@ -19,6 +19,32 @@ For more information about: - Deprecated and removed features, see [Deprecated Engine Features](../deprecated.md). - Changes to the Engine API, see [Engine API version history](../api/version-history.md). +## 25.0.1 + +{{< release-date date="2024-01-23" >}} + +For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: + +- [docker/cli, 25.0.1 milestone](https://github.com/docker/cli/issues?q=is%3Aclosed+milestone%3A25.0.1) +- [moby/moby, 25.0.1 milestone](https://github.com/moby/moby/issues?q=is%3Aclosed+milestone%3A25.0.1) + +### Bug fixes and enhancements + +- API: Fix incorrect HTTP status code for containers with an invalid network configuration created before upgrading to Docker Engine v25.0. [moby/moby#47159](https://github.com/moby/moby/pull/47159) +- Ensure that a MAC address based on a container's IP address is re-generated when the container is stopped and restarted, in case the generated IP/MAC addresses have been reused. [moby/moby#47171](https://github.com/moby/moby/pull/47171) +- Fix `host-gateway-ip` not working during build when not set through configuration. [moby/moby#47192](https://github.com/moby/moby/pull/47192) +- Fix a bug that prevented a container from being renamed twice. [moby/moby#47196](https://github.com/moby/moby/pull/47196) +- Fix an issue causing containers to have their short ID added to their network alias when inspecting them. [moby/moby#47182](https://github.com/moby/moby/pull/47182) +- Fix an issue in detecting whether a remote build context is a Git repository. [moby/moby#47136](https://github.com/moby/moby/pull/47136) +- Fix an issue with layers order in OCI manifests. [moby/moby#47150](https://github.com/moby/moby/issues/47150) +- Fix volume mount error when passing an `addr` or `ip` mount option. [moby/moby#47185](https://github.com/moby/moby/pull/47185) +- Improve error message related to extended attributes that can't be set due to improperly namespaced attribute names. [moby/moby#47178](https://github.com/moby/moby/pull/47178) +- Swarm: Fixed `start_interval` not being passed to the container config. [moby/moby#47163](https://github.com/moby/moby/pull/47163) + +### Packaging updates + +- Upgrade Compose to `2.24.2`. [docker/docker-ce-packaging#981](https://github.com/docker/docker-ce-packaging/pull/981) + ## 25.0.0 {{< release-date date="2024-01-19" >}} @@ -153,3 +179,47 @@ For a full list of pull requests and changes in this release, refer to the relev - Deprecate API versions older than 1.24. [Deprecation notice](../deprecated.md#deprecate-legacy-api-versions) - Deprecate `IsAutomated` field and `is-automated` filter for `docker search`. [Deprecation notice](../deprecated.md#isautomated-field-and-is-automated-filter-on-docker-search) - API: Deprecate `Container` and `ContainerConfig` properties for `/images/{id}/json` (`docker image inspect`). [moby/moby#46939](https://github.com/moby/moby/pull/46939) + +### Known limitations + +#### Extended attributes for tar files + +In this release, the code that handles `tar` archives was changed to be more +strict and to produce an error when failing to write extended attributes +(`xattr`). The `tar` implementation for macOS generates additional extended +attributes by default when creating tar files. These attribute prefixes aren't +valid Linux `xattr` namespace prefixes, which causes an error when Docker +attempts to process these files. For example, if you try to use a tar file with +an `ADD` Dockerfile instruction, you might see an error message similar to the +following: + +```text +failed to solve: lsetxattr /sftp_key.ppk: operation not supported +``` + +Error messages related to extended attribute validation were improved to +include more context in [v25.0.1](#2501), but the limitation in Docker being +unable to process the files remains. Tar files created with the macOS `tar` +using default arguments will produce an error when the tar file is used with +Docker. + +As a workaround, if you need to use tar files with Docker generated on macOS, +you can either: + +- Use the `--no-xattr` flag for the macOS `tar` command to strip **all** the + extended attributes. If you want to preserve extended attributes, this isn't + a recommended option. +- Install and use `gnu-tar` to create the tarballs on macOS instead of the + default `tar` implementation. To install `gnu-tar` using Homebrew: + + ```console + $ brew install gnu-tar + ``` + + After installing, add the `gnu-tar` binary to your `PATH`, for example by + updating your `.zshrc` file: + + ```console + $ echo 'PATH="/opt/homebrew/opt/gnu-tar/libexec/gnubin:$PATH"' >> ~/.zshrc + $ source ~/.zshrc + ```