Issue #1640 (rm --force) unfixed, but otherwise LGTM
SELinux issues (filed #1560, investigating one more). Systemd-in-container not working ("Failed to allocate manager object"; I'm still investigating). Otherwise LGTM.
Totally broken; do not use. Fix is under discussion.
With containernetworking-plugins-0.7.3-2.fc29
, passes the expected subset of docker-autotest. LGTM, but I'm not adding karma because I agree that the RPM requirements should be updated to specify the above containernetworking-plugins.
Tested install over containernetworking-cni-0.7.1-1.fc29
: worked fine. (Also confirmed that containernetworking-plugins-0.7.3-1.fc29, the previous build, does not install cleanly on top of containernetworking-cni. I.e. the rpm Obsoletes is now correct).
Then tested ugrade from 0.7.3-1; that too worked fine.
Also ran docker-autotest suite, all fine.
LGTM.
Passes most of docker-autotest. New failures in build
subtest; could just be harmless behavioral differences. Am investigating and will file issues if necessary, otherwise LGTM.
If I were to suggest updating the RPM, adding a dependency on container-selinux >= 2:2.71
, would I need to go into hiding for my own protection?
Passes (expected subset of) docker-autotest suite.
That worked: it brings in the desired runc from updates-testing
. Now running test suite, will LGTM once that passes (which I'm expecting).
Still doesn't pull in the required runc. Could it be the missing epoch?
# rpm -qp --requires podman-0.8.5-4.gitdc5a711.fc28.x86_64.rpm |grep runc
runc >= 1.0.0-51
# rpm -q --provides runc
runc = 2:1.0.0-50.dev.git20aff4f.fc28
runc(x86-64) = 2:1.0.0-50.dev.git20aff4f.fc28
^^-----
I see runc >= 1.0.0-50
but that doesn't actually work: the required release is -51
. (Yes, I've tested. With runc-1.0.0-50.dev.git20aff4f.fc28, I see the tmpfs crash)
@baude, would you mind rebuilding with a new RPM dependency?
Requires: runc >= 2:1.0.0-51
With runc-2:1.0.0-46.dev.gitb4e2ecb, this podman build fails when run with --tmpfs
(libpod issue 1396). Thank you!
Two regressions: no error thrown on invalid command, and --tmpfs broken. Filed issues #1395 and #1396 respectively. Neither are glaring showstoppers, but I'm not quite prepared to give it karma. Sorry.
LGTM. Tried upgrading from podman-0.8.3-1
and 0.8.4-1
; the former correctly replaced containernetworking-cni
with -plugins
; the latter simply upgraded -plugins
from 0.7.3-1
to -2
. In all cases, docker-autotest suite passes the expected tests (now including the tcp/udp issue, #735).
Won't install for me either:
Upgrading:
podman x86_64 0.8.4-1.git9f9b8cf.fc28 updates-testing 6.7 M
Installing dependencies:
containernetworking-plugins x86_64 0.7.3-1.fc28 updates-testing 12 M
.....
Error: Transaction check error:
file /usr/libexec/cni/bridge from install of containernetworking-plugins-0.7.3-1.fc28.x86_64 conflicts with file from package containernetworking-cni-0.7.1-1.fc28.x86_64
(and many more of those)
LGTM. Passes all the expected docker-autotest subtests.
LGTM. podman-0.8.3-1.git9d09a4d.fc28 passes expected subset of docker-autotest.
Passes much of docker-autotest suite; one weird failure in iptables, will continue investigating tomorrow.