Name: | podman |
---|---|
Version: | 1.6.4 |
Release: | 18.0.1.el7_8 |
Architecture: | aarch64 |
Group: | Unspecified |
Size: | 59323838 |
License: | ASL 2.0 |
RPM: | podman-1.6.4-18.0.1.el7_8.aarch64.rpm |
Source RPM: | podman-1.6.4-18.0.1.el7_8.src.rpm |
Build Date: | Wed May 13 2020 |
Build Host: | ca-buildarm04.us.oracle.com |
Vendor: | Oracle America |
URL: | https://podman.io/ |
Summary: | Manage Pods, Containers and Container Images |
Description: | podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool. podman provides a Docker-CLI comparable command line that eases the transition from other container engines and allows the management of pods, containers and images. Simply put: alias docker=podman. Most podman commands can be run as a regular user, without requiring additional privileges. podman uses Buildah(1) internally to create container images. Both tools share image (not container) storage, hence each can use or manipulate images (but not containers) created by the other. Manage Pods, Containers and Container Images libpod Simple management tool for pods, containers and images |
- Reduce unnecessary writable mounts in NaiveDiffDriver [Orabug: 31025483] - handle redirect from the docker registry v2 [Orabug: 29874238] (nikita.gerasimov@oracle.com)
- fix "CVE-2020-8945 proglottis/gpgme: Use-after-free in GPGME bindings during container image pull" - Resolves: #1806940
- fix "CVE-2020-10696 buildah: crafted input tar file may lead to local file overwriting during image build process" - Resolves: #1817743
- use the full PR 5348 to fix "no route to host from inside container" - Resolves: #1806895
- update fix for "podman (1.6.4) rhel 8.1 no route to host from inside container" - Resolves: #1806895
- fix "CVE-2020-1702 podman: containers/image: Container images read entire image manifest into memory" - Resolves: #1810614
- fix "[FJ8.2 Bug]: [REG]The "--group-add" option of "podman create" doesn't function." - Resolves: #1808702
- fix "Podman can't reuse a container name, even if the container that was using it is no longer around" - Resolves: #1807437
- fix "podman exec does not reads from stdin" - Resolves: #1807586
- fix "podman (1.6.4) rhel 8.1 no route to host from inside container" - Resolves: #1806895