Bug 1271367 - [DOCS] Enhance "Using Images" Docker topic
[DOCS] Enhance "Using Images" Docker topic
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Alex Dellapenta
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2015-10-13 14:40 EDT by Alex Dellapenta
Modified: 2018-05-17 08:05 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-05-17 08:05:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alex Dellapenta 2015-10-13 14:40:24 EDT
Original GH Issue: https://github.com/openshift/openshift-docs/issues/589

Enhance the following section on using arbitrary Docker images:


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:


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 15:12:26 EDT
Got peer review, pending tech review from Eng in PR:


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