Skip to content

Commit 86bded7

Browse files
committed
document pulling images locally
1 parent 1013c84 commit 86bded7

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/configure.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,7 @@ Configuration steps in this file depend on [jq](https://stedolan.github.io/jq/),
6060
- [Configure custom PostgreSQL](#configure-custom-postgres)
6161
- [Install without RBAC](#install-without-rbac)
6262
- [Use non-default namespace](#use-non-default-namespace)
63+
- [Pulling images locally](#pulling-images-locally)
6364

6465
## Configure network access
6566

@@ -499,3 +500,13 @@ Sourcegraph's Kubernetes deployment [requires an Enterprise license key](https:/
499500
If you're deploying Sourcegraph into a non-default namespace,
500501
refer to [base/prometheus/README.md#Namespaces](../base/prometheus/README.md#Namespaces) and
501502
[base/grafana/README.md#Namespaces](../base/grafana/README.md#Namespaces) for further configuration instructions.
503+
504+
## Pulling images locally
505+
506+
In some cases, a site admin may want to pull all Docker images used in the cluster locally. For
507+
example, if your organization requires use of a private registry, you may need to do this as an
508+
intermediate step to mirroring them on the private registry. The following script accomplishes this:
509+
510+
```bash
511+
for IMAGE in $(grep -FR 'image:' . | awk '{ print $(NF) }'); do docker pull $IMAGE; done;
512+
```

0 commit comments

Comments
 (0)