"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "RELEASE_NOTES.md" between
podman-3.2.2.tar.gz and podman-3.2.3.tar.gz

About: podman (previous name "libpod") provides a library for applications looking to use the Container Pod concept, popularized by Kubernetes. Podman manages pods, containers, container images, and container volumes.

RELEASE_NOTES.md  (podman-3.2.2):RELEASE_NOTES.md  (podman-3.2.3)
# Release Notes # Release Notes
## 3.2.3
### Security
- This release addresses CVE-2021-3602, an issue with the `podman build` command
with the `--isolation chroot` flag that results in environment variables from t
he host leaking into build containers.
### Bugfixes
- Fixed a bug where events related to images could occur before the relevant ope
ration had completed (e.g. an image pull event could be written before the pull
was finished) ([#10812](https://github.com/containers/podman/issues/10812)).
- Fixed a bug where `podman save` would refuse to save images with an architectu
re different from that of the host ([#10835](https://github.com/containers/podma
n/issues/10835)).
- Fixed a bug where the `podman import` command did not correctly handle images
without tags ([#10854](https://github.com/containers/podman/issues/10854)).
- Fixed a bug where Podman's journald events backend would fail and prevent Podm
an from running when run on a host with systemd as PID1 but in an environment (e
.g. a container) without systemd ([#10863](https://github.com/containers/podman/
issues/10863)).
- Fixed a bug where containers using rootless CNI networking would fail to start
when the `dnsname` CNI plugin was in use and the host system's `/etc/resolv.con
f` was a symlink ([#10855](https://github.com/containers/podman/issues/10855) an
d [#10929](https://github.com/containers/podman/issues/10929)).
- Fixed a bug where containers using rootless CNI networking could fail to start
due to a race in rootless CNI initialization ([#10930](https://github.com/conta
iners/podman/issues/10930)).
### Misc
- Updated Buildah to v1.21.3
- Updated the containers/common library to v0.38.16
## 3.2.2 ## 3.2.2
### Changes ### Changes
- Podman's handling of the Architecture field of images has been relaxed. Since 3.2.0, Podman required that the architecture of the image match the architecture of the system to run containers based on an image, but images often incorrectly report architecture, causing Podman to reject valid images ([#10648](https://gi thub.com/containers/podman/issues/10648) and [#10682](https://github.com/contain ers/podman/issues/10682)). - Podman's handling of the Architecture field of images has been relaxed. Since 3.2.0, Podman required that the architecture of the image match the architecture of the system to run containers based on an image, but images often incorrectly report architecture, causing Podman to reject valid images ([#10648](https://gi thub.com/containers/podman/issues/10648) and [#10682](https://github.com/contain ers/podman/issues/10682)).
- Podman no longer uses inotify to monitor for changes to CNI configurations. Th is removes potential issues where Podman cannot be run because a user has exhaus ted their available inotify sessions ([#10686](https://github.com/containers/pod man/issues/10686)). - Podman no longer uses inotify to monitor for changes to CNI configurations. Th is removes potential issues where Podman cannot be run because a user has exhaus ted their available inotify sessions ([#10686](https://github.com/containers/pod man/issues/10686)).
### Bugfixes ### Bugfixes
- Fixed a bug where the `podman cp` would, when given a directory as its source and a target that existed and was a file, copy the contents of the directory int o the parent directory of the file; this now results in an error. - Fixed a bug where the `podman cp` would, when given a directory as its source and a target that existed and was a file, copy the contents of the directory int o the parent directory of the file; this now results in an error.
- Fixed a bug where the `podman logs` command would, when following a running co ntainer's logs, not include the last line of output from the container when it e xited when the `k8s-file` driver was in use ([#10675](https://github.com/contain ers/podman/issues/10675)). - Fixed a bug where the `podman logs` command would, when following a running co ntainer's logs, not include the last line of output from the container when it e xited when the `k8s-file` driver was in use ([#10675](https://github.com/contain ers/podman/issues/10675)).
- Fixed a bug where Podman would fail to run containers if `systemd-resolved` wa s incorrectly detected as the system's DNS server ([#10733](https://github.com/c ontainers/podman/issues/10733)). - Fixed a bug where Podman would fail to run containers if `systemd-resolved` wa s incorrectly detected as the system's DNS server ([#10733](https://github.com/c ontainers/podman/issues/10733)).
- Fixed a bug where the `podman exec -t` command would only resize the exec sess ion's TTY after the session started, leading to a race condition where the termi nal would initially not have a size set ([#10560](https://github.com/containers/ podman/issues/10560)). - Fixed a bug where the `podman exec -t` command would only resize the exec sess ion's TTY after the session started, leading to a race condition where the termi nal would initially not have a size set ([#10560](https://github.com/containers/ podman/issues/10560)).
 End of changes. 1 change blocks. 
0 lines changed or deleted 31 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)