Documentation Index
Fetch the complete documentation index at: https://docs.langchain.com/llms.txt
Use this file to discover all available pages before exploring further.
By default, LangSmith will pull images from our public Docker registry. However, if you are running LangSmith in an environment that does not have internet access, or if you would like to use a private Docker registry, you can mirror the images to your own registry and then configure your LangSmith installation to use those images.
Requirements
- Authenticated access to a Docker registry that your Kubernetes cluster/machine has access to.
- Docker installed on your local machine or a machine that has access to the Docker registry.
- A Kubernetes cluster where you can run LangSmith.
Mirroring the images
For your convenience, we have provided a script that will mirror the images for you. You can find the script in the LangSmith Helm Chart repository
To use the script, you will need to run the script with the following command specifying your registry and platform:
bash mirror_images.sh <your-registry> [<platform>]
<your-registry> is the URL of your Docker registry (e.g. myregistry.com) and <platform> is the platform you are using (e.g. linux/amd64, linux/arm64, etc.). If you do not specify a platform, it will default to linux/amd64.
For example, if your registry is myregistry.com, your platform is linux/arm64, and you want to use the latest version of the images, you would run:
bash mirror_langsmith_images.sh --registry myregistry --platform linux/arm64 --version 0.10.66
values.yaml file of the LangSmith Helm Chart. These can be found here: LangSmith Helm Chart values.yaml
Here is an example of how to mirror the images using Docker:
# Pull the images from the public registry
docker pull langchain/langsmith-backend:latest
docker tag langchain/langsmith-backend:latest <your-registry>/langsmith-backend:latest
docker push <your-registry>/langsmith-backend:latest
Configuration
Once the images are mirrored, you will need to configure your LangSmith installation to use the mirrored images. You can do this by modifying the values.yaml file for your LangSmith Helm Chart installation. Replace tag with the version you want to use, e.g. 0.10.66 for the latest version at the time of writing.
images:
imagePullSecrets: [] # Add your image pull secrets here if needed
registry: "" # Set this to your registry URL if you mirrored all images to the same registry using our script. Then you can remove the repository prefix from the images below.
aceBackendImage:
repository: "(your-registry)/langchain/langsmith-ace-backend"
pullPolicy: IfNotPresent
tag: "0.10.66"
backendImage:
repository: "(your-registry)/langchain/langsmith-backend"
pullPolicy: IfNotPresent
tag: "0.10.66"
frontendImage:
repository: "(your-registry)/langchain/langsmith-frontend"
pullPolicy: IfNotPresent
tag: "0.10.66"
hostBackendImage:
repository: "(your-registry)/langchain/hosted-langserve-backend"
pullPolicy: IfNotPresent
tag: "0.10.66"
operatorImage:
repository: "(your-registry)/langchain/langgraph-operator"
pullPolicy: IfNotPresent
tag: "6cc83a8"
platformBackendImage:
repository: "(your-registry)/langchain/langsmith-go-backend"
pullPolicy: IfNotPresent
tag: "0.10.66"
playgroundImage:
repository: "(your-registry)/langchain/langsmith-playground"
pullPolicy: IfNotPresent
tag: "0.10.66"
postgresImage:
repository: "(your-registry)/postgres"
pullPolicy: IfNotPresent
tag: "14.7"
redisImage:
repository: "(your-registry)/redis"
pullPolicy: IfNotPresent
tag: "7"
clickhouseImage:
repository: "(your-registry)/clickhouse/clickhouse-server"
pullPolicy: Always
tag: "24.8"
Additional images for Fleet and Insights
If you are using Fleet or Insights, the LangGraph operator dynamically creates Redis and PostgreSQL (pgvector) pods for each deployment. These pods use images defined in operator templates that require separate configuration.
You must mirror these additional images:
docker.io/redis:7docker.io/pgvector/pgvector:pg15
Then override the operator templates in your values.yaml to use your mirrored images:
operator:
templates:
redis: |
apiVersion: apps/v1
kind: Deployment
metadata:
name: ${service_name}
namespace: ${namespace}
spec:
replicas: 1
selector:
matchLabels:
app: ${service_name}
template:
metadata:
labels:
app: ${service_name}
spec:
enableServiceLinks: false
containers:
- name: redis
image: (your-registry)/redis:7
ports:
- containerPort: 6379
name: redis
livenessProbe:
exec:
command:
- redis-cli
- ping
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
tcpSocket:
port: 6379
initialDelaySeconds: 10
periodSeconds: 5
db: |
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: ${service_name}
spec:
serviceName: ${service_name}
selector:
matchLabels:
app: ${service_name}
persistentVolumeClaimRetentionPolicy:
whenDeleted: Delete
whenScaled: Retain
template:
metadata:
labels:
app: ${service_name}
spec:
containers:
- name: postgres
image: (your-registry)/pgvector/pgvector:pg15
ports:
- containerPort: 5432
command: ["docker-entrypoint.sh"]
args:
- postgres
- -c
- max_connections=${max_connections}
env:
- name: PGDATA
value: /var/lib/postgresql/data/pgdata
volumeMounts:
- name: postgres-data
mountPath: /var/lib/postgresql/data
enableServiceLinks: false
volumeClaimTemplates:
- metadata:
name: postgres-data
spec:
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: "${storage_gi}Gi"
(your-registry) with your registry URL. The template variables (${service_name}, ${namespace}, ${max_connections}, ${storage_gi}) are replaced by the operator at runtime and must be kept as-is.
Once configured, you will need to update your LangSmith installation. You can follow our upgrade guide here: Upgrading LangSmith. If your upgrade is successful, your LangSmith instance should now be using the mirrored images from your Docker registry.
