I've had more problems than Ed. I've had to dnf -y update runc --enablerepo updates-testing && runc both, but when I run a container I'm seeing no output.
Edsantiago pinged me via e-mail he suggested updating container-selinux too, and that turned the trick. Baseline tests pass after updating container-selinux and runc.
This update has been submitted for testing by dwalsh.
This update has obsoleted podman-0.8.5-4.gitdc5a711.fc28, and has inherited its bugs and notes.
That worked: it brings in the desired runc from
updates-testing. Now running test suite, will LGTM once that passes (which I'm expecting).Passes (expected subset of) docker-autotest suite.
Looks good. I tested a basic use case.
karma: +1
I've had more problems than Ed. I've had to
dnf -y update runc --enablerepo updates-testing&& runc both, but when I run a container I'm seeing no output.I'd expect to see the root directories files.
Edsantiago pinged me via e-mail he suggested updating container-selinux too, and that turned the trick. Baseline tests pass after updating container-selinux and runc.
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?This update has been pushed to testing.
This update has been pushed to testing.
This update has been obsoleted by podman-0.9.1-3.gitaba58d1.fc28.