FEDORA-2019-fe6ef87556 — enhancement update for podman

stable

podman-1.3.1-1.git7210727.fc29

FEDORA-2019-fe6ef87556 created by dwalsh 3 years ago for Fedora 29

Latest version of podman

How to install

sudo dnf upgrade --refresh --advisory=FEDORA-2019-fe6ef87556

This update has been submitted for testing by dwalsh.

3 years ago

baude commented & provided feedback 3 years ago

karma

lgtm

BZ#1703139 `podman ps -s` crashes!!

adrian commented & provided feedback 3 years ago

karma

Upgrading from podman-1:1.2.0-2.git3bd528e.fc29.x86_64 to podman-1:1.3.1-1.git7210727.fc29.x86_64 breaks my nextcloud container:

# /usr/bin/podman --log-level debug run --name nextcloud-fpm --net host         -v /home/containers/nextcloud/html:/var/www/html         -v /home/containers/nextcloud/apps:/var/www/html/custom_apps         -v /home/con
tainers/nextcloud/config:/var/www/html/config         -v /home/containers/nextcloud/data:/var/www/html/data         nextcloud:fpmoauth
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/lib/containers/storage
DEBU[0000] Using run root /var/run/containers/storage
DEBU[0000] Using static dir /var/lib/containers/storage/libpod
DEBU[0000] Using tmp dir /var/run/libpod
DEBU[0000] Using volume path /var/lib/containers/storage/volumes 
DEBU[0000] Set libpod namespace to ""                   
DEBU[0000] [graphdriver] trying provided driver "overlay" 
DEBU[0000] overlay test mount with multiple lowers succeeded 
DEBU[0000] overlay test mount indicated that metacopy is not being used 
DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=true, usingMetacopy=false 
DEBU[0000] Initializing event backend file              
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]docker.io/library/nextcloud:fpmoauth" 
DEBU[0000] reference "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]docker.io/library/nextcloud:fpmoauth" does not resolve to an image ID 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]localhost/nextcloud:fpmoauth" 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]@f07a50f1e3c254b18c15c614356bf74674cf25ac37cba4afe274ef4bf61baedb" 
DEBU[0000] exporting opaque data as blob "sha256:f07a50f1e3c254b18c15c614356bf74674cf25ac37cba4afe274ef4bf61baedb" 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]@f07a50f1e3c254b18c15c614356bf74674cf25ac37cba4afe274ef4bf61baedb" 
DEBU[0000] exporting opaque data as blob "sha256:f07a50f1e3c254b18c15c614356bf74674cf25ac37cba4afe274ef4bf61baedb" 
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev]@f07a50f1e3c254b18c15c614356bf74674cf25ac37cba4afe274ef4bf61baedb" 
DEBU[0000] User mount /home/containers/nextcloud/html:/var/www/html options [] 
DEBU[0000] User mount /home/containers/nextcloud/apps:/var/www/html/custom_apps options [] 
DEBU[0000] User mount /home/containers/nextcloud/config:/var/www/html/config options [] 
DEBU[0000] User mount /home/containers/nextcloud/data:/var/www/html/data options [] 
ERRO[0000] conflict at mount destination /var/www/html: duplicate mount destination

I am running podman usually from systemd as root. I have reverted back to podman-1.2.0-2

santiago commented & provided feedback 3 years ago

One regression (#980). One flake which I won't have time to pursue until Monday:

# podman --cgroup-manager=cgroupfs run -d -i --name=memory_positive_Fjb4 -m 5246976 registry.access.redhat.com/rhel7/rhel:latest /bin/bash

Error: container create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:390: setting cgroup config for procHooks process caused \\\"failed to write 10493952 to memory.memsw.limit_in_bytes: write /sys/fs/cgroup/memory/libpod_parent/libpod-b9c562426e6ef066ed15b3ec369f8124e46c95539693384f8490410dcb211813/memory.memsw.limit_in_bytes: device or resource busy\\\"\""
                                 : internal libpod error

Two other failures that look suspicious but again I can't pursue until next week.

This update has been pushed to testing.

3 years ago

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

3 years ago

jwakely commented & provided feedback 3 years ago

Fixes bug #1688562 (rootless "podman build" doesn't allow network access). I haven't tested other functionality.

BZ#1688562 rootless "podman build" doesn't allow network access

BZ#1695492 /usr/libexec/podman is not owned by any package

rishi commented & provided feedback 3 years ago

karma

One regression that breaks the Silverblue toolbox:

$ podman images --filter "label=com.github.debarshiray.toolbox=true"
Error: invalid filter syntax label=com.github.debarshiray.toolbox=true

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

3 years ago

This update has been submitted for stable by dwalsh.

3 years ago

This update has been pushed to stable.

3 years ago

Please login to add feedback.

Metadata

Type

enhancement

Karma

-1

Signed

Content Type

RPM

Test Gating

ignored

Builds

podman-1.3.1-1.git7210727.fc29

Settings

Unstable by Karma

-3

Stable by Karma

disabled

Stable by Time

disabled

Dates

submitted

3 years ago

in testing

3 years ago

in stable

3 years ago

BZ#1688562 rootless "podman build" doesn't allow network access

BZ#1695492 /usr/libexec/podman is not owned by any package

BZ#1696679 Cannot create UNIX sockets in podman (SELinux denial)

BZ#1702705 rootless podman always fail if selinux is disabled

BZ#1702787 podman top doesn't accept the same arguments as docker top

BZ#1703139 `podman ps -s` crashes!!

podman-1.3.1-1.git7210727.fc29

Automated Test Results

ignored