Update release notes for v1.6.0 #4030
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-robot
added
approved
|
@QiWang19 a PR like this is the first step in the Podman release process. We look at all the PRs tagged with the appropriate label ( |
RELEASE_NOTES.md
Outdated
| ### Features | ||
| - The `podman network create`, `podman network rm`, `podman network inspect`, and `podman network ls` commands have been added to manage CNI networks used by Podman | ||
| - The `podman volume create` command can now create and mount volumes with options, allowing volumes backed by NFS, tmpfs, and many other filesystems | ||
| - Podman can now run containers without CGroups for better integration with systemd via the `--cgroups=disabled` flag to `podman create` and `podman run`. This is presently only supported with the `crun` OCI runtime |
There was a problem hiding this comment.
suggest "systemd by using the --cgroups=disabled option with the podman create and podman run commands"
RELEASE_NOTES.md
Outdated
| - The `podman network create`, `podman network rm`, `podman network inspect`, and `podman network ls` commands have been added to manage CNI networks used by Podman | ||
| - The `podman volume create` command can now create and mount volumes with options, allowing volumes backed by NFS, tmpfs, and many other filesystems | ||
| - Podman can now run containers without CGroups for better integration with systemd via the `--cgroups=disabled` flag to `podman create` and `podman run`. This is presently only supported with the `crun` OCI runtime | ||
| - The `podman volume rm` and `podman volume inspect` commands can now refer to volumes by unambiguous partial name, in addition to full name (e.g. `podman volume rm myvol` to remove a volume named `myvolume`) ([#3891](https://github.com/containers/libpod/issues/3891)) |
There was a problem hiding this comment.
s/an unambiguous/unambigous
| - Mounting volumes into a container using `--volume`, `--mount`, and `--tmpfs` now allows the `suid`, `dev`, and `exec` mount options (the inverse of `nosuid`, `nodev`, `noexec`) ([#3819](https://github.com/containers/libpod/issues/3819)) | ||
| - The `podman push` command now supports the `--digestfile` option to save a file containing the pushed digest | ||
| - Pods can now have their hostname set via `podman pod create --hostname` or providing Pod YAML with a hostname set to `podman play kube` ([#3732](https://github.com/containers/libpod/issues/3732)) | ||
| - The `podman image sign` command now supports the `--cert-dir` flag |
| - The `podman push` command now supports the `--digestfile` option to save a file containing the pushed digest | ||
| - Pods can now have their hostname set via `podman pod create --hostname` or providing Pod YAML with a hostname set to `podman play kube` ([#3732](https://github.com/containers/libpod/issues/3732)) | ||
| - The `podman image sign` command now supports the `--cert-dir` flag | ||
| - The `podman run` and `podman create` commands now support the `--security-opt label=filetype:$LABEL` flag to set the SELinux label for container files |
| - Fixed a bug where rootless Podman could not run `podman exec` when the container was not run inside a CGroup owned by the user ([#3937](https://github.com/containers/libpod/issues/3937)) | ||
| - Fixed a bug where `podman play kube` would panic when given Pod YAML without a `securityContext` ([#3956](https://github.com/containers/libpod/issues/3956)) | ||
| - Fixed a bug where Podman would place files incorrectly when `storage.conf` configuration items were set to the empty string ([#3952](https://github.com/containers/libpod/issues/3952)) | ||
| - Fixed a bug where `podman build` did not correctly inherit Podman's CGroup configuration, causing crashed on CGroups V2 systems ([#3938](https://github.com/containers/libpod/issues/3938)) |
There was a problem hiding this comment.
Based on what I found in https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html, I'm never capitalizing 'cgroup' and never pluralizing it. YMMV.
|
I think I'm going to keep We might want to go in with sed and hit all of them at once, though. |
mheon
force-pushed
the
release_notes_1.6.0
branch
from
19b2816 to
125ee44
Compare
RELEASE_NOTES.md
Outdated
|
|
||
| ### Misc | ||
| - Significant changes were made to Podman volumes in this release. If you have pre-existing volumes, it is strongly recommended to run `podman system renumber` after upgrading. | ||
| - Podman now uses the CNI firewall plugin, requiring at least version 0.8.1 of the CNI plugins are installed |
There was a problem hiding this comment.
I'm not sure what you're trying to say after the comma here? Perhaps "requiring at least version 0.8.1 for the CNI plugins to be installed"
RELEASE_NOTES.md
Outdated
| - Updated vendored Buildah to v1.11.2 | ||
| - Improved error messages when trying to run `podman pause` or `podman stats` on a rootless container on a system without CGroups V2 enabled | ||
| - `TMPDIR` has been set to `/var/tmp` by default to better handle large temporary files | ||
| - Waiting for containers has been optimized to detect container stop more rapidly |
There was a problem hiding this comment.
suggest "container stop" to "container stoppage" or perhaps "that the container has stopped"
RELEASE_NOTES.md
Outdated
| - Podman containers now include a `ContainerManager` annotation indicating they were created by `libpod`. | ||
| - The `podman info` command now includes information about `slirp4netns` and `fuse-overlayfs` if they are available | ||
| - Podman no longer sets a default size of 65kb for tmpfs filesystems | ||
| - The default Podman CNI network has been renamed in an attempt to prevent conflicts with CRI-O when both are run on the same system. This should only take effect on system restart. |
There was a problem hiding this comment.
I luv the ending period, but you don't seem to have them elsewhere! sigh
Signed-off-by: Matthew Heon <[email protected]>
mheon
force-pushed
the
release_notes_1.6.0
branch
from
125ee44 to
4c2694f
Compare
openshift-ci-robot
added
the
do-not-merge/hold
|
/lgtm |
| - Fixed a bug where rootless Podman could not run `podman exec` when the container was not run inside a CGroup owned by the user ([#3937](https://github.com/containers/libpod/issues/3937)) | ||
| - Fixed a bug where `podman play kube` would panic when given Pod YAML without a `securityContext` ([#3956](https://github.com/containers/libpod/issues/3956)) | ||
| - Fixed a bug where Podman would place files incorrectly when `storage.conf` configuration items were set to the empty string ([#3952](https://github.com/containers/libpod/issues/3952)) | ||
| - Fixed a bug where `podman build` did not correctly inherit Podman's CGroup configuration, causing crashed on CGroups V2 systems ([#3938](https://github.com/containers/libpod/issues/3938)) |
There was a problem hiding this comment.
sorry , just spotted. s/crashes/crashed/
| - Fixed a bug where `podman varlink` would hang when managed by systemd due to SD_NOTIFY support conflicting with Varlink ([#3572](https://github.com/containers/libpod/issues/3572)) | ||
|
|
||
| ### Misc | ||
| - Significant changes were made to Podman volumes in this release. If you have pre-existing volumes, it is strongly recommended to run `podman system renumber` after upgrading. |
|
Just found two more nits. Feel free to ignore them, but if by chance you need to make other changes, please nab them. |
|
/hold cancel |
openshift-ci-robot
removed
the
do-not-merge/hold
github-actions
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.
As the title says