Name: | podman |
---|---|
Version: | 1.6.4 |
Release: | 23.0.1.module+el8.3.0+9619+9eeb6ed6 |
Architecture: | aarch64 |
Module: | container-tools:2.0:8030020201124142243:3ba8ebeb |
Group: | Unspecified |
Size: | 50662399 |
License: | ASL 2.0 |
RPM: | podman-1.6.4-23.0.1.module+el8.3.0+9619+9eeb6ed6.aarch64.rpm |
Source RPM: | podman-1.6.4-23.0.1.module+el8.3.0+9619+9eeb6ed6.src.rpm |
Build Date: | Mon Dec 21 2020 |
Build Host: | ca-buildarm05 |
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] - delivering fix for [Orabug: 29874238] by Nikita Gerasimov <nikita.gerasimov@oracle.com>
- fix "podman run with --rm errors out/segfaults in container-tools-2.0-8.3.0" - Resolves: #1875289
- sync with 1.6.4-rhel branch to avoid regression - Resolves: #1879092
- fix "podman run with --rm errors out/segfaults on rhel8.3" - Resolves: #1875289
- bump release to preserve upgrade path - Related: #1868603
- fix "[2.0-8.3.0] Podman does not use --tmpdir when pulling an image" - Related: #1868603
- exclude i686 arch - Related: #1821193
- bump release to preserve upgrade path - Related: #1821193
- fix "CVE-2020-10696 buildah: crafted input tar file may lead to local file overwriting during image build process" - Resolves: #1819391
- use the full PR 5348 to fix "no route to host from inside container" - Resolves: #1806899