Merge pull request #50620 from sounix000/4175-S2I-tasks-failing

RHDEVDOCS-4175 Document that all S2I tasks are failing and the solution

Author: rolfedh

modules/op-release-notes-1-7.adoc

@@ -409,7 +409,17 @@ time="2022-03-04T09:47:57Z" level=error msg="error writing \"0 0 4294967295\\n\"
 time="2022-03-04T09:47:57Z" level=error msg="(unable to determine exit status)"
 ----
 +
-With this update, the `pipelines-scc` security context constraint (SCC) is compatible with the `SETFCAP` capability necessary for S2I and Buildah clustertasks. As a result, the S2I build tasks run successfully.
+With this update, the `pipelines-scc` security context constraint (SCC) is compatible with the `SETFCAP` capability necessary for `Buildah` and `S2I` cluster tasks. As a result, the `Buildah` and `S2I` build tasks can run successfully.
++
+To successfully run the `Buildah` cluster task and `S2I` build tasks for applications written in various languages and frameworks, add the following snippet for appropriate `steps` objects such as `build` and `push`:
++
+[source,yaml]
+----
+securityContext:
+  capabilities:
+    add: ["SETFCAP"]
+----
++
 // https://issues.redhat.com/browse/SRVKP-2091
 
 

modules/op-release-notes-1-8.adoc

@@ -494,13 +494,23 @@ This update fixes the issue. It passes the namespace-based configuration to the
 
 * Before this update, all S2I build tasks failed with an error similar to the following message:
 +
+[source,terminal]
 ----
 Error: error writing "0 0 4294967295\n" to /proc/22/uid_map: write /proc/22/uid_map: operation not permitted
 time="2022-03-04T09:47:57Z" level=error msg="error writing \"0 0 4294967295\\n\" to /proc/22/uid_map: write /proc/22/uid_map: operation not permitted"
 time="2022-03-04T09:47:57Z" level=error msg="(unable to determine exit status)"
 ----
 +
-With this update, the `pipelines-scc` security context constraint (SCC) is compatible with the `SETFCAP` capability necessary for S2I and Buildah cluster tasks. As a result, the S2I build tasks run successfully.
+With this update, the `pipelines-scc` security context constraint (SCC) is compatible with the `SETFCAP` capability necessary for `Buildah` and `S2I` cluster tasks. As a result, the `Buildah` and `S2I` build tasks can run successfully.
++
+To successfully run the `Buildah` cluster task and `S2I` build tasks for applications written in various languages and frameworks, add the following snippet for appropriate `steps` objects such as `build` and `push`:
++
+[source,yaml]
+----
+securityContext:
+  capabilities:
+    add: ["SETFCAP"]
+----
 +
 // (borrowed from 1.7.2 release notes) https://issues.redhat.com/browse/SRVKP-2091
 // Piyush Garg