https://lists.fedoraproject.org/pipermail/devel/2015-July/212180.html
---
fedora-atomic-docker-host.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/fedora-atomic-docker-host.json b/fedora-atomic-docker-host.json
index 4bed86a..766212d 100644
--- a/fedora-atomic-docker-host.json
+++
Sadly, no, the only step you missed was disabling SELinux.
https://github.com/GoogleCloudPlatform/kubernetes/issues/2630
Is where Paul is tracking his work around these problems.
On Fri, 2015-07-17 at 09:50 +0200, Tobias Florek wrote:
Hi,
using the following atomic host version I can't
Pushed, thanks!
(minor: I deleted the trailing period to match the commit style)
Hi Joe,
Thanks for getting back to me.
I'm in an environment where I can't choose images of my choice, the only
[relevant] ones I have available are CentOS 6 7 and RHEL 6 7.
I know that Red Hat developed kpatch https://en.wikipedia.org/wiki/Kpatch;
which enables hot-patching
Hi,
using the following atomic host version I can't access secret volumes
from within pods due to an AVC and selinux denying it. Is there some
setup step that I am missing?
os-version:
atomic host status:
2015-07-15 23:33:20 22.61 db540a53ba fedora-atomic
i.e.
