From d40a8713eb70d0c9b68cee9ca6093fb6f711c318 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Mon, 8 May 2023 16:33:58 -0400 Subject: [PATCH] OCPBUGS13238: CoreOS Layering docs should have info about using the cluster pull-secret --- modules/coreos-layering-configuring.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/coreos-layering-configuring.adoc b/modules/coreos-layering-configuring.adoc index ae85a08b35..064f5cdc5d 100644 --- a/modules/coreos-layering-configuring.adoc +++ b/modules/coreos-layering-configuring.adoc @@ -44,6 +44,8 @@ RUN rpm-ostree override replace https://example.com/hotfixes/haproxy-1.0.16-5.el Instructions on how to create a Containerfile are beyond the scope of this documentation. ==== +* Because the process for building a custom layered image is performed outside of the cluster, you must use the `--authfile /path/to/pull-secret` option with Podman or Buildah. Alternatively, to have the pull secret read by these tools automatically, you can add it to one of the default file locations: `~/.docker/config.json`, `$XDG_RUNTIME_DIR/containers/auth.json`, `~/.docker/config.json`, or `~/.dockercfg`. Refer to the `containers-auth.json` man page for more information. + * You must push the custom layered image to a repository that your cluster can access. .Procedure