Comments
miabbott
I used rpm-ostree override replace on F28 Atomic Host Beta to install this update.
docker run -it docker.io/busybox echo "PASS" worked for me
But I still can't do oc cluster up using origin-clients-3.6.0-1. Fails with the same error in BZ 1558425
Ran through the tutorial here and all was well: https://github.com/projectatomic/libpod/blob/master/docs/tutorials/podman_tutorial.md
This fixes https://github.com/projectatomic/atomic/issues/1176 for me and doesn't appear to break anything else, so +1 from me.
I reported the following issue related to SELinux labels on files landed by system containers - https://github.com/projectatomic/atomic/issues/1176
From the discussion, I'm not sure if the default_t label is correct for those files, but it is currently tripping up some of our automated tests.
This fixes the issue of being unable to retrieve content over HTTP2 for me.
Additionally, BZ#1510139 still seems to persist with this build
Additionally, BZ#1510139 still seems to persist with this build
I replaced the selinux-policy packages on a Fedora 27 Atomic Host with this build and ran into the following BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1525589
Tested on Fedora 26 Atomic Host
Tested on F27 Atomic Host
This passed our sanity checks using F27 Atomic Host updates-testing branch.
ran our rpm-ostree test suite from atomic-host-tests and all was well
The docker daemon starts up successfully and you can (mostly) use it as normal. But BZ #1510139 still persists.
Basic checks of atomic, docker, and skopeo worked for me
On a Fedora 26 Cloud system with this 'docker' update installed, I still can't run containers because of problems in /etc/docker/seccomp.json
I don't know why bodhi won't take my mixed karma...
Anyways, the BZ is not fixed, but as I said earlier, simple 'docker run' seems to work ok.