Skip to content

[enterprise-4.12] RHDEVDOCS-4175 Document that all S2I tasks are failing and the solution #51550

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2022
Merged

[enterprise-4.12] RHDEVDOCS-4175 Document that all S2I tasks are failing and the solution #51550

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion modules/op-release-notes-1-7.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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


Expand Down
12 changes: 11 additions & 1 deletion modules/op-release-notes-1-8.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down