[CI:DOCS] Add release notes for v5.0.0 #21963
Merged
Conversation
This file contains 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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
openshift-ci
bot
added
the
approved
baude
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| ### Features | ||
| - VMs created by `podman machine` can now use the native Apple hypervisor (`applehv`) when run on MacOS. | ||
| - A new command has been added, `podman machine reset`, which will remove all existing `podman machine` VMs and relevant configurations. | ||
| - The default image to use with `podman machine` VMs can now be set from `containers.conf`. |
baude
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| - VMs created by `podman machine` can now use the native Apple hypervisor (`applehv`) when run on MacOS. | ||
| - A new command has been added, `podman machine reset`, which will remove all existing `podman machine` VMs and relevant configurations. | ||
| - The default image to use with `podman machine` VMs can now be set from `containers.conf`. | ||
| - The `podman manifest add` command now supports a new `--artifact` option which will create an artifact manifest including one or more files as OCI artifacts and add them to the specified manifest list. |
There was a problem hiding this comment.
if this is accurate wording, then maybe we could rework this sentence to simplify it
eriksjolund
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| - Fixed a bug where the `podman image scp` command could fail if there was not sufficient space in the destination machine's `/tmp` for the image ([#21239](https://github.com/containers/podman/issues/21239)). | ||
| - Fixed a bug where containers killed by running out of memory (including due to a memory limit) were not properly marked as OOM killed in `podman inspect` ([#13102](https://github.com/containers/podman/issues/13102)). | ||
| - Fixed a bug where `podman kube play` did not create memory-backed emptyDir volumes using a tmpfs filesystem. | ||
| - Fixed a bug where containers started with `--rm` were sometimes not removed affter a reboot ([#21482](https://github.com/containers/podman/issues/21482)). |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where containers started with `--rm` were sometimes not removed affter a reboot ([#21482](https://github.com/containers/podman/issues/21482)). | |
| - Fixed a bug where containers started with `--rm` were sometimes not removed after a reboot ([#21482](https://github.com/containers/podman/issues/21482)). |
eriksjolund
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
|
|
||
| ### API | ||
| - A new API endpoint, `/libpod/images/$name/resolve`, has been added to resolve a (potential) short name to a list of fully-qualified image references Podman which could be used to pull the image. | ||
| - Fixed a bug where the List API for Images did not properly handle filters and would discard all the the last listed filter. |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug where the List API for Images did not properly handle filters and would discard all the the last listed filter. | |
| - Fixed a bug where the List API for Images did not properly handle filters and would discard all but the last listed filter. |
(I guess the description is related to #21260)
eriksjolund
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| - Connections from `podman system connection` and farms from `podman farm` are now written to a new configuration file called `podman-connections.conf`. As a result, Podman no longer writes to `containers.conf`. Existing connections from `containers.conf` will still be respected. | ||
| - Most `podman farm` subcommands (save for `podman farm build`) no longer need to connect to the machines in the farm to run. | ||
| - The `podman create` and `podman run` commands no longer require specifying an entrypoint on the command line when the container image does not define one. In this case, an empty command will be passed to the OCI runtime, and the resulting behavior is runtime-specific. | ||
| - Default SELinux labels for content mounted from the host in `podman machine` VMs on Mac is now `system_u:object_r:nfs_t:s0` so it can be shared with all containers without issue. |
There was a problem hiding this comment.
Suggested change
| - Default SELinux labels for content mounted from the host in `podman machine` VMs on Mac is now `system_u:object_r:nfs_t:s0` so it can be shared with all containers without issue. | |
| - Default SELinux label for content mounted from the host in `podman machine` VMs on Mac is now `system_u:object_r:nfs_t:s0` so that it can be shared with all containers without issue. |
eriksjolund
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| - The backend for the `podman machine` commands has seen extensive rewrites. Configuration files have changed format and VMs from Podman 4.x and earlier are no longer usable. `podman machine` VMs must be recreated with Podman 5. | ||
| - The `podman machine init` command now pulls images as OCI artifacts, instead of using HTTP. As a result, a valid `policy.json` file is required on the host. Windows and Mac installers have been changed to install this file. | ||
| - QEMU is no longer a supported VM provider for `podman machine` on Mac. Instead, the native Apple hypervisor is supported. | ||
| - The `ConfigPath` and `Image` fields are not longer provided by the `podman machine inspect` command. Users can also no longer use `{{ .ConfigPath }}` or `{{ .Image }}` as arguments to `podman machine inspect --format`. |
There was a problem hiding this comment.
Suggested change
| - The `ConfigPath` and `Image` fields are not longer provided by the `podman machine inspect` command. Users can also no longer use `{{ .ConfigPath }}` or `{{ .Image }}` as arguments to `podman machine inspect --format`. | |
| - The `ConfigPath` and `Image` fields are no longer provided by the `podman machine inspect` command. Users can also no longer use `{{ .ConfigPath }}` or `{{ .Image }}` as arguments to `podman machine inspect --format`. |
eriksjolund
reviewed
Mar 6, 2024
RELEASE_NOTES.md
Outdated
| - Podman now supports a new global option, `--config`, to point to a Docker configuration where we can source registry login credentials. | ||
| - The `podman ps --format` command now supports a new format specifier, `.Label` ([#20957](https://github.com/containers/podman/issues/20957)). | ||
| - The `uidmapping` and `gidmapping` options to the `podman run --userns=auto` option can now map to host IDs by prefixing host IDs with the `@` symbol. | ||
| - Quadlet now support systemd-style drop-in directories. |
There was a problem hiding this comment.
Suggested change
| - Quadlet now support systemd-style drop-in directories. | |
| - Quadlet now supports systemd-style drop-in directories. |
|
Comments addressed, re-pushed |
Luap99
reviewed
Mar 7, 2024
RELEASE_NOTES.md
Outdated
| - The output of `podman events --format "{{json .}}"` has been changed to improve Docker compatibility, including the `time` and `timeNano` fields ([#14993](https://github.com/containers/podman/issues/14993)). | ||
| - The name of `podman machine` VMs and the username used within the VM are now validated and must match this regex: `[a-zA-Z0-9][a-zA-Z0-9_.-]*`. | ||
| - Using multiple filters with the List Images REST API now combines the filters with AND instead of OR, improving Docker compatibility ([#18412](https://github.com/containers/podman/issues/18412)). | ||
| - The parsing for a number of Podman CLI options which accept arrays has been changed to no longer accept string-delineated lists, and instead to require the option to be passed multiple times. These options are `--annotation` to `podman manifest annotate` and `podman manifest add`, the `--configmap`, `--log-opt`, and `--annotation` options to `podman kube play`, the `--pubkeysfile` option to `podman image trust set`, the `--encryption-key` and `--decryption-key` options to `podman create`, `podman run`, `podman push` and `podman pull`, the `--env-file` option to `podman exec`, the `--bkio-weight-device`, `--device-read-bps`, `--device-write-bps` `--device-read-iops`, `--device-write-iops`, `--device`, `--label-file`, ``--chrootdirs`, `--log-opt`, and `--env-file` options to `podman create` and `podman run`, and the `--hooks-dir` and `--module` global options. |
There was a problem hiding this comment.
Suggested change
| - The parsing for a number of Podman CLI options which accept arrays has been changed to no longer accept string-delineated lists, and instead to require the option to be passed multiple times. These options are `--annotation` to `podman manifest annotate` and `podman manifest add`, the `--configmap`, `--log-opt`, and `--annotation` options to `podman kube play`, the `--pubkeysfile` option to `podman image trust set`, the `--encryption-key` and `--decryption-key` options to `podman create`, `podman run`, `podman push` and `podman pull`, the `--env-file` option to `podman exec`, the `--bkio-weight-device`, `--device-read-bps`, `--device-write-bps` `--device-read-iops`, `--device-write-iops`, `--device`, `--label-file`, ``--chrootdirs`, `--log-opt`, and `--env-file` options to `podman create` and `podman run`, and the `--hooks-dir` and `--module` global options. | |
| - The parsing for a number of Podman CLI options which accept arrays has been changed to no longer accept string-delineated lists, and instead to require the option to be passed multiple times. These options are `--annotation` to `podman manifest annotate` and `podman manifest add`, the `--configmap`, `--log-opt`, and `--annotation` options to `podman kube play`, the `--pubkeysfile` option to `podman image trust set`, the `--encryption-key` and `--decryption-key` options to `podman create`, `podman run`, `podman push` and `podman pull`, the `--env-file` option to `podman exec`, the `--bkio-weight-device`, `--device-read-bps`, `--device-write-bps` `--device-read-iops`, `--device-write-iops`, `--device`, `--label-file`, `--chrootdirs`, `--log-opt`, and `--env-file` options to `podman create` and `podman run`, and the `--hooks-dir` and `--module` global options. |
RELEASE_NOTES.md
Outdated
| ### API | ||
| - A new API endpoint, `/libpod/images/$name/resolve`, has been added to resolve a (potential) short name to a list of fully-qualified image references Podman which could be used to pull the image. | ||
| - Fixed a bug where the List API for Images did not properly handle filters and would discard all but the last listed filter. | ||
| - Fixed a bug in the Docker Create API for COntainers where entries from `/etc/hosts` were copied into create containers, resulting in incompatibility with network aliases. |
There was a problem hiding this comment.
Suggested change
| - Fixed a bug in the Docker Create API for COntainers where entries from `/etc/hosts` were copied into create containers, resulting in incompatibility with network aliases. | |
| - Fixed a bug in the Docker Create API for Containers where entries from `/etc/hosts` were copied into create containers, resulting in incompatibility with network aliases. |
RELEASE_NOTES.md
Outdated
| - Fixed a bug where `podman machine` VMs using the HyperV provider could not mount shares on directories that did not yet exist. | ||
| - Fixed a bug where the `podman compose` command did not respect the `--connection` and `--url` options. | ||
| - Fixed a bug where the `podman stop -t -1` command would wait for 0 seconds, not infinite seconds, before sending SIGKILL ([#21811](https://github.com/containers/podman/issues/21811)). | ||
| - Fixed a bug where Podman could deadlock when cleaning up a container when the `slirp4netns` network mode was used with a restart policy of `always` or `unless-stopped` or `on-failure` and a user namespace ([#21522](https://github.com/containers/podman/pull/21522)). |
There was a problem hiding this comment.
is linking to the pull request intentional?
Signed-off-by: Matt Heon <[email protected]>
mheon
force-pushed
the
release_notes_500
branch
from
005da1d to
0fdd831
Compare
|
Comments addressed, added release notes from things from the last few days |
|
/lgtm |
openshift-merge-bot
bot
merged commit 87896d3
into
containers:main
43 of 44 checks passed
stale-locking-app
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Took a lot longer than it should have, but we have release notes.
Does this PR introduce a user-facing change?