So far we've not explicitly called out SELinux as a prereq to running with 'oc
cluster up' because to try OpenShift it's really not absolutely necessary. You
may be running Docker for Windows or Docker for Mac which don't have SELinux.
It does make sense that if you intend to run your application on an official
OpenShift cluster you should develop in an environment that has SELinux
enabled, but local development is only one use case for running cluster up.
> On Dec 1, 2016, at 7:24 AM, Steve Kuznetsov <skuzn...@redhat.com> wrote:
> I've not had any issues running development workflows, including `oc cluster
> up/down`, with SELinux enforcing. Cesar can give a more authoritative answer
> for `oc cluster`, but FWIW I don't know of any compelling reason today to
> turn off SELinux for OpenShift development.
> On Dec 1, 2016 2:28 AM, "Lalatendu Mohanty" <lmoha...@redhat.com
> <mailto:lmoha...@redhat.com>> wrote:
> As per documentation  SELinux is a prerequisite for OpenShift
> installation. However for "oc cluster up/down" environment there is no
> mention of SELinux .
> Is it ok if an application developed in OpenShift environment provided by "oc
> cluster up" that is without SELinux or SELinux disabled and then we try to
> run it in a proper OpenShift environment with SELinux enabled?
> Going by my SELinux experience, I think we should keep SELinux enabled in the
> development environment as it would in the production environment, else it
> can completely break the application. But the lack of documentation and
> understanding around role of SELinux in "oc cluster up" environment led to
> some confusion .
> Can someone shed some light on this? Thanks a lot in advance.
>  https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md
>  https://github.com/minishift/minishift-centos-iso/issues/1
> dev mailing list
> firstname.lastname@example.org <mailto:email@example.com>
dev mailing list