Skip to content

Commit a4d5f3d

Browse files
authored
Merge pull request #48456 from rolfedh/RHDEVDOCS-2587
RHDEVDOCS-2587 Bug 1810904 - [DOC]Should document how to configure pu…
2 parents b101b6f + e64ea54 commit a4d5f3d

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

modules/builds-image-source.adoc

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
//
33
// * builds/creating-build-inputs.adoc
44

5+
:_content-type: CONCEPT
6+
57
[id="builds-image-source_{context}"]
68
= Image source
79

@@ -46,7 +48,9 @@ source:
4648
If your cluster uses an `ImageContentSourcePolicy` object to configure repository mirroring, you can use only global pull secrets for mirrored registries. You cannot add a pull secret to a project.
4749
====
4850

49-
Optionally, if an input image requires a pull secret, you can link the pull secret to the service account used by the build. By default, builds use the `builder` service account. The pull secret is automatically added to the build if the secret contains a credential that matches the repository hosting the input image. To link a pull secret to the service account used by the build, run:
51+
.Images that require pull secrets
52+
53+
When using an input image that requires a pull secret, you can link the pull secret to the service account used by the build. By default, builds use the `builder` service account. The pull secret is automatically added to the build if the secret contains a credential that matches the repository hosting the input image. To link a pull secret to the service account used by the build, run:
5054

5155
[source,terminal]
5256
----
@@ -60,12 +64,9 @@ This feature is not supported for builds using the custom strategy.
6064
====
6165
endif::[]
6266

63-
/////
64-
[role="_additional-resources"]
65-
.Additional resources
67+
.Images on mirrored registries that require pull secrets
6668

67-
* Custom Strategy
68-
ifndef::openshift-online[]
69-
* ImageStreamTags
70-
endif::[]
71-
/////
69+
When using an input image from a mirrored registry, if you get a `build error: failed to pull image` message, you can resolve the error by using either of the following methods:
70+
71+
* Create an input secret that contains the authentication credentials for the builder image’s repository and all known mirrors. In this case, create a pull secret for credentials to the image registry and its mirrors.
72+
* Use the input secret as the pull secret on the `BuildConfig` object.

0 commit comments

Comments
 (0)