Debugging tool for pods and images

Edit Package podman

podman is a simple client only tool to help with debugging issues when daemons such as CRI runtime and the kubelet are not responding or failing. A shared API layer could be created to share code between the daemon and podman. podman does not require any daemon running. podman utilizes the same underlying components that crio uses i.e. containers/image, container/storage, oci-runtime-tool/generate, runc or any other OCI compatible runtime. podman shares state with crio and so has the capability to debug pods/images created by crio.

Refresh
Refresh
Source Files
Filename Size Changed
README.SUSE.SLES 0000000595 595 Bytes
_service 0000000580 580 Bytes
_servicedata 0000000238 238 Bytes
podman-3.3.1.tar.xz 0006490324 6.19 MB
podman-rpmlintrc 0000000316 316 Bytes
podman.changes 0000220908 216 KB
podman.conf 0000000048 48 Bytes
podman.spec 0000008432 8.23 KB
Revision 85 (latest revision is 134)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 917154 from Richard Brown's avatar Richard Brown (RBrownSUSE) (revision 85)
- require runc >= 1.0.1

- Update to version 3.3.1:
  * Bugfixes
    - Fixed a bug where unit files created by podman generate systemd could 
      not cleanup shut down containers when stopped by systemctl stop (#11304).
    - Fixed a bug where podman machine commands would not properly locate 
      the gvproxy binary in some circumstances.
    - Fixed a bug where containers created as part of a pod using the 
      --pod-id-file option would not join the pod's network namespace (#11303).
    - Fixed a bug where Podman, when using the systemd cgroups driver, 
      could sometimes leak dbus sessions.
    - Fixed a bug where the until filter to podman logs and podman events 
      was improperly handled, requiring input to be negated (#11158).
    - Fixed a bug where rootless containers using CNI networking run on 
      systems using systemd-resolved for DNS would fail to start if resolved 
      symlinked /etc/resolv.conf to an absolute path (#11358).
  * API
    - A large number of potential file descriptor leaks from improperly closing 
      client connections have been fixed.

- Revert crun change due to crun having exclusive arch targets
  that would drop podman support in PPC and IBM Z

- Update to version 3.3.0:
  * Fix network aliases with network id
  * machine: compute sha256 as we read the image file
  * machine: check for file exists instead of listing directory
  * pkg/bindings/images.nTar(): slashify hdr.Name values
  * Volumes: Only remove from DB if plugin removal succeeds
Comments 1

Shyukri Shyukriev's avatar

Is it and option to show at least notification that /etc/subuid and /etc/subgid needs to include your user?

https://opensource.com/article/19/2/how-does-rootless-podman-work

openSUSE Build Service is sponsored by