Skip to content

Commit e550f2f

Browse files
authored
Merge pull request #22520 from nkakkar81/RHDEVDOCS-1922
KI and Manual Workaround for Buildah ClusterTask in Pipelines 1.0
2 parents 333a4dc + ba8db5f commit e550f2f

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

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

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,45 @@ For this release, use flags `disable-home-env-overwrite` and `disable-working-di
7272
== Known issues
7373
* If you are upgrading from an older version of {pipelines-title}, you must delete your existing deployments before upgrading to {pipelines-title} version 1.0. To delete an existing deployment, you must first delete Custom Resources and then uninstall the {pipelines-title} Operator. For more details, see the uninstalling {pipelines-title} section.
7474
* Submitting the same `v1alpha1` Tasks more than once results in an error. Use `oc replace` instead of `oc apply` when re-submitting a `v1alpha1` Task.
75+
* The `buildah` ClusterTask does not work when a new user is added to a container.
76+
+
77+
When the Operator is installed, the `--storage-driver` flag for the `buildah` ClusterTask is not specified, therefore the flag is set to its default value. In some cases, this causes the storage driver to be set incorrectly. When a new user is added, the incorrect storage-driver results in the failure of the `buildah` ClusterTask with the following error:
78+
+
79+
----
80+
useradd: /etc/passwd.8: lock file already used
81+
useradd: cannot lock /etc/passwd; try again later.
82+
----
83+
+
84+
As a workaround, manually set the `--storage-driver` flag value to `overlay` in the `buildah-task.yaml` file:
85+
+
86+
. Login to your cluster as a `cluster-admin`:
87+
+
88+
----
89+
$ oc login -u <login> -p <password> https://openshift.example.com:6443
90+
----
91+
. Use the `oc edit` command to edit `buildah` ClusterTask:
92+
+
93+
----
94+
$ oc edit clustertask buildah
95+
----
96+
+
97+
The current version of the `buildah` clustertask YAML file opens in the editor set by your `EDITOR` environment variable.
98+
. Under the `steps` field, locate the following `command` field:
99+
+
100+
----
101+
command: ['buildah', 'bud', '--format=$(params.FORMAT)', '--tls-verify=$(params.TLSVERIFY)', '--layers', '-f', '$(params.DOCKERFILE)', '-t', '$(resources.outputs.image.url)', '$(params.CONTEXT)']
102+
----
103+
104+
. Replace the `command` field with the following:
105+
+
106+
----
107+
command: ['buildah', '--storage-driver=overlay', 'bud', '--format=$(params.FORMAT)', '--tls-verify=$(params.TLSVERIFY)', '--no-cache', '-f', '$(params.DOCKERFILE)', '-t', '$(params.IMAGE)', '$(params.CONTEXT)']
108+
----
109+
. Save the file and exit.
110+
111+
112+
+
113+
Alternatively, you can also modify the `buildah` ClusterTask YAML file directly on the web console by navigating to *Pipelines* -> *Cluster Tasks* -> *buildah*. Select *Edit Cluster Task* from the *Actions* menu and replace the `command` field as shown in the previous procedure.
75114

76115
[id="fixed-issues-1-0_{context}"]
77116
== Fixed issues

0 commit comments

Comments
 (0)