Skip to content

Commit c4fee1b

Browse files
author
OpenShift Bot
committed
Merge pull request #3726 from smarterclayton/update_readme
Merged by openshift-bot
2 parents 9553f7a + 9c2ef58 commit c4fee1b

File tree

1 file changed

+12
-9
lines changed

1 file changed

+12
-9
lines changed

README.md

+12-9
Original file line numberDiff line numberDiff line change
@@ -35,21 +35,24 @@ NOTE: OpenShift Origin 1.0 has been released [releases page](https://github.com/
3535

3636
Security!!!
3737
-------------------
38-
OpenShift is a system that runs Docker containers on your machine. In some cases (build operations) it does so using privileged containers. Those containers access your host's Docker daemon and perform `docker build` and `docker push` operations. As such, you should be aware of the inherent security risks associated with performing `docker build` operations on arbitrary images as they have effective root access. This is particularly relevant when running the OpenShift as a node directly on your laptop or primary workstation. Only build and run code you trust.
38+
OpenShift runs with the following security policy by default:
3939

40-
For more information on the security of containers, see these articles:
41-
42-
* http://opensource.com/business/14/7/docker-security-selinux
43-
* https://docs.docker.com/articles/security/
44-
45-
Consider using images from trusted parties, building them yourself on OpenShift, or only running containers that run as non-root users.
40+
* Containers run as a non-root unique user that is separate from other system users
41+
* They cannot access host resources, run privileged, or become root
42+
* They are given CPU and memory limits defined by the system administrator
43+
* Any persistent storage they access will be under a unique SELinux label, which prevents others from seeing their content
44+
* These settings are per project, so containers in different projects cannot see each other by default
45+
* Regular users can run Docker, source, and custom builds
46+
* By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the `builds/docker` and `builds/custom` policy resource.
47+
* Regular users and project admins cannot change their security quotas.
4648

49+
See the [security documentation](https://docs.openshift.org/latest/admin_guide/manage_scc.html) for more on managing these restrictions.
4750

4851
Getting Started
4952
---------------
50-
The easiest way to run OpenShift Origin is in a Docker container (OpenShift requires Docker 1.6 or higher or 1.6.2 on CentOS/RHEL):
53+
The easiest way to run OpenShift Origin is in a Docker container (OpenShift requires Docker 1.6.2 or higher):
5154

52-
**Important!**: Docker 1.7 changed mount propagation to PRIVATE, which [breaks](https://github.com/openshift/origin/issues/3072) running OpenShift inside a container. If you are on Docker 1.7 you will need to use the [Vagrant](CONTRIBUTING.adoc#develop-on-virtual-machine-using-vagrant) or binary installation paths.
55+
**Important!**: Docker on non-RedHat distributions (Ubuntu, Debian, boot2docker) has mount propagation PRIVATE, which [breaks](https://github.com/openshift/origin/issues/3072) running OpenShift inside a container. Please use the [Vagrant](CONTRIBUTING.adoc#develop-on-virtual-machine-using-vagrant) or binary installation paths on those distributions.
5356

5457
$ sudo docker run -d --name "origin" \
5558
--privileged --net=host \

0 commit comments

Comments
 (0)