Comments

269 Comments
karma

Also, doesn't work out of the box:

# podman ps
podman: symbol lookup error: podman: undefined symbol: seccomp_api_get

Seems to require libseccomp-2.4.1-0.fc29. Could someone please add the appropriate Requires?

karma

Passes docker-autotest except for regressions #3302 and #3359.

karma

Passes docker-autotest except for regressions #3302 and #3359.

karma

LGTM. #980 (regression) and #3302 (intermittent weirdness with attach) are IMO minor.

Confirmed that /usr/libexec/crio* are gone.

karma

LGTM. #980 (regression) and #3302 (intermittent weirdness with attach) are IMO minor.

Confirmed that /usr/libexec/crio* are gone.

Passes most of docker-autotest; regression on issue #980

I do believe that the addition of %{_libexecdir}/crio in 898cc75 is a mistake that should be reverted.

karma

Passes most of docker-autotest; regression on issue #980

I do believe that the addition of %{_libexecdir/crio in 8ee8c09 is a mistake that should be reverted.

One regression (#980). Two other failures that look suspicious but I won't have time to pursue until Monday.

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.

Ran through docker-autotest; LGTM

Ran docker-autotest on podman-1.2.0-2.git3bd528e.fc29; no regressions or problems seen.

Two regressions: #2823 and 2824. I think the latter merits a new build.

Tested with podman; lgtm

LGTM

Minor issues (#2473 and #2530); otherwise LGTM

@dustymabe too many to list. All are fixed in master, 1.1.1 coming soon.

I'm gonna have to vote for 1.1.1.

Sorry for not catching these earlier. I have test setups optimized for testing RPMs; nothing that will (without lots of manual effort) build from sources.

Installs cleanly. Ran test suite against mildly-tweaked podman-1.0, passes expected tests. LGTM.