Add release notes for v5.7.0-rc1 #27353
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
release-note-none
approved
RELEASE_NOTES.md
Outdated
| ## 5.7.0 | ||
| ### Features | ||
| - The remote Podman client and `podman system service` API server now support encrypting connections with TLS and mTLS, including client authentication by certificate ([#24583](https://github.com/containers/podman/issues/24583)). | ||
| - The `podman system connection add` command can now create connections to TCP sockets with by TLS and mTLS encryption. |
There was a problem hiding this comment.
Suggested change
| - The `podman system connection add` command can now create connections to TCP sockets with by TLS and mTLS encryption. | |
| - The `podman system connection add` command can now create connections to TCP sockets with TLS and mTLS encryption. |
RELEASE_NOTES.md
Outdated
| - When running the `podman image load` and `podman build` commands against a `podman machine` VM, if the path being loaded or built is shared into the VM, Podman will load it from the VM's filesystem instead of streaming the data through the REST API, improving performance ([#26321](https://github.com/containers/podman/issues/26321)). | ||
| - A default location for container log files when using the `k8s-file` log driver can now be specified with the `log_path` option in `containers.conf`. | ||
| - Default flags for the OCI runtime can now be set with the `runtimes_flags` option in `containers.conf`. | ||
| - The `podman artifact remove` command can now accept multiple arguments, e.g. `podman artifact rm artifact1 artifact2`. |
There was a problem hiding this comment.
Suggested change
| - The `podman artifact remove` command can now accept multiple arguments, e.g. `podman artifact rm artifact1 artifact2`. | |
| - The `podman artifact remove` command can now accept multiple arguments, e.g., `podman artifact rm artifact1 artifact2`. |
RELEASE_NOTES.md
Outdated
| - The `podman quadlet print` command now has a new alias, `podman quadlet cat` ([#27296](https://github.com/containers/podman/issues/27296)). | ||
| - The remote Podman client's `podman artifact remove` command now supports the `--all` option. | ||
| - The `podman artifact add` command now supports a new option, `--replace`, which will replace any existing artifact with the given name ([#27082](https://github.com/containers/podman/issues/27082)). | ||
| - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remote an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). |
There was a problem hiding this comment.
Suggested change
| - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remote an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). | |
| - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remove an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). |
RELEASE_NOTES.md
Outdated
| - Podman now requires Go 1.24. | ||
| - When the `-p`/`--publish` and `--network=ns:/path` options are used together when creating a container, Podman will not warn that the `-p` option will be ignored as an existing namespace is in use (this has always been the case, but Podman now prints a warning about it) ([#26663](https://github.com/containers/podman/issues/26663)). | ||
| - The `podman stats` command now provides additional information about container resource utilization when run on FreeBSD. | ||
| - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run` and the `--interface-name` option to `podman network create`. |
There was a problem hiding this comment.
Suggested change
| - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run` and the `--interface-name` option to `podman network create`. | |
| - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run`, and the `--interface-name` option to `podman network create`. |
RELEASE_NOTES.md
Outdated
| - Podman can now optionally be built with Sequoia-PGP support. When so built, the `--sign-by-sq-fingerprint` option allows signing images using Seqoia-PGP keys. | ||
|
|
||
| ### Bugfixes | ||
| - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker which matched substrings ([#26623](https://github.com/containers/podman/issues/26623)). |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker which matched substrings ([#26623](https://github.com/containers/podman/issues/26623)). | |
| - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker, which matched substrings ([#26623](https://github.com/containers/podman/issues/26623)). |
RELEASE_NOTES.md
Outdated
| ### API | ||
| - Added a new API endpoint to list quadlets (`GET /libpod/quadlets/json`). | ||
| - The Compat Inspect endpoint for Images no longer includes the `ContainerConfig` field. To access image configuration, use the `Config` field instead. This matches changes made by Docker in the v1.45 API. | ||
| - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. | |
| - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), Push, Commit, and the Pull endpoints for Images (compat & libpod), and the Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. |
RELEASE_NOTES.md
Outdated
| - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. | ||
|
|
||
| ### Misc | ||
| - Error messages returned when an incomplete `--device` option (e.g. `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. |
There was a problem hiding this comment.
Suggested change
| - Error messages returned when an incomplete `--device` option (e.g. `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. | |
| - Error messages returned when an incomplete `--device` option (e.g., `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. |
|
|
||
| ## 5.6.2 | ||
| ### Bugfixes | ||
| - Fixed a bug where stopping the `podman machine start` command with SIGPIPE could result in machine state being stuck as "Starting" ([#26949](https://github.com/containers/podman/issues/26949)). |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where stopping the `podman machine start` command with SIGPIPE could result in machine state being stuck as "Starting" ([#26949](https://github.com/containers/podman/issues/26949)). | |
| - Fixed a bug where stopping the `podman machine start` command with SIGPIPE could result in the machine state being stuck as "Starting" ([#26949](https://github.com/containers/podman/issues/26949)). |
There was a problem hiding this comment.
Too late on this one, it's copied from the 5.6.2 release notes from that branch
| - Updated the containers/image library to v5.38.0 | ||
| - Updated the containers/storage library to v1.61.0 | ||
| - Updated the containers/common library to v0.66.0 | ||
| - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo. |
There was a problem hiding this comment.
Maybe, or maybe not, your call.:
Suggested change
| - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo. | |
| - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo. As a result, the vendored entries have changed from github.com/containers/common to go.podman.io/common, for example. |
There was a problem hiding this comment.
Ehh. This is mostly for users and packagers, I don't think folks reading this need to know
| ### Bugfixes | ||
| - Fixed a bug where network creation and removal events were displayed incorrectly when the `journald` events driver was in use. | ||
| - Fixed a bug where the `--security-opt seccomp=unconfined` option was broken on Windows ([#26855](https://github.com/containers/podman/issues/26855)). | ||
| - Fixed a bug where containers created with a name longer than 64 characters, no explicit hostname, the the `container_name_as_hostname` option in `containers.conf` set to `true` would fail to start. |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where containers created with a name longer than 64 characters, no explicit hostname, the the `container_name_as_hostname` option in `containers.conf` set to `true` would fail to start. | |
| - Fixed a bug where containers created with a name longer than 64 characters, no explicit hostname, the `container_name_as_hostname` option in `containers.conf` set to `true` would fail to start. |
There was a problem hiding this comment.
Same as above, too late to change
| - Fixed a bug where Podman would fail to start containers when runc 1.3.0 or later was used as the OCI runtime ([#26938](https://github.com/containers/podman/issues/26938)). | ||
|
|
||
| ### Misc | ||
| - Adjusted the systemd-tmpfiles script to recursively remove temporary files directories placed in `/tmp`, ensuring proper operation of Podman after a reboot if `/tmp` is not a tmpfs. |
There was a problem hiding this comment.
Suggested change
| - Adjusted the systemd-tmpfiles script to recursively remove temporary files directories placed in `/tmp`, ensuring proper operation of Podman after a reboot if `/tmp` is not a tmpfs. | |
| - Adjusted the systemd-tmpfiles script to recursively remove temporary file directories placed in `/tmp`, ensuring proper operation of Podman after a reboot if `/tmp` is not a tmpfs. |
|
A bunch of nits for consideration, otherwise LGTM |
mheon
force-pushed
the
release_notes_570_rc1
branch
from
370a6f0 to
172f455
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@containers/podman-maintainers PTAL and merge |
l0rd
reviewed
Oct 24, 2025
RELEASE_NOTES.md
Outdated
|
|
||
| ### Changes | ||
| - In preparation for a planned removal of the BoltDB database in Podman 6.0, a warning has been added for installations still using BoltDB. These warnings were added in Podman 5.6, but were not visible by default; they now are. They can be suppressed with the `SUPPRESS_BOLTDB_WARNING=true` environment variable. | ||
| - The Windows installer has been redesigned with a simpler single MSI architecture that supports both user-scope (no admin required) and machine-scope installations. Note: Users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). |
There was a problem hiding this comment.
A small suggestion: since the old Windows installer is still here, the new one is (currently) an alternative.
Suggested change
| - The Windows installer has been redesigned with a simpler single MSI architecture that supports both user-scope (no admin required) and machine-scope installations. Note: Users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). | |
| - There is a new Windows installer, with a simpler single MSI architecture, that supports both user-scope (no admin required) and machine-scope installations. The old installer is also released for backward compatibility. Note: Users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). |
Signed-off-by: Matt Heon <matthew.heon@pm.me>
mheon
force-pushed
the
release_notes_570_rc1
branch
from
172f455 to
9b57510
Compare
|
Other than the possible change that @l0rd suggested, |
|
And it looks like you addressed that one already. |
openshift-merge-bot
bot
merged commit 9d1f283
into
containers:v5.7
32 of 40 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In preparation for v5.7.0-rc1
Does this PR introduce a user-facing change?