Bug 1271367 - [DOCS] Enhance "Using Images" Docker topic
Summary: [DOCS] Enhance "Using Images" Docker topic
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Alex Dellapenta
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 18:40 UTC by Alex Dellapenta
Modified: 2018-05-17 12:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-17 12:05:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alex Dellapenta 2015-10-13 18:40:24 UTC
Original GH Issue: https://github.com/openshift/openshift-docs/issues/589

Enhance the following section on using arbitrary Docker images:

https://docs.openshift.com/enterprise/3.0/using_images/docker_images/overview.html

It does now at least link to the admin task about RunAsAny, but it needs more context. E.g., only a cluster-admin could even do what is being suggested. Also, it should be more up front in this "Using Images" topic about the security risks. Probably do an "include" on the following security warning, versus a passive link:

https://docs.openshift.com/enterprise/3.0/install_config/install/prerequisites.html#security-warning

We could also actually show an example of how you could now do something w/ that image if the SCC was indeed adjusted appropriately by the cluster-admin (e.g., show a walkthrough of a user grabbing an arbitrary image and getting it running in OpenShift).

Some related info in "Support Arbitrary User IDs" in https://docs.openshift.com/enterprise/3.0/creating_images/guidelines.html#openshift-specific-guidelines.

Comment 3 Alex Dellapenta 2018-05-14 19:12:26 UTC
Got peer review, pending tech review from Eng in PR:

https://github.com/openshift/openshift-docs/pull/9247


Note You need to log in before you can comment on or make changes to this bug.