You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
Explore how to write a docker-compose.override.yaml file with our current executor distribution so that we can loosely bundle privileged executors on compose deployments. Findings should be added to product documentation (on installing/configuring executors).
The text was updated successfully, but these errors were encountered:
version: '2.4'services:
executor:
container_name: executorimage: 'index.docker.io/sourcegraph/executor:insiders@sha256:4909f85ba9b2446cf7c901dc735f265493b50e90acaf4cc0d36bac11d8c0d1b4'cpus: 1mem_limit: '4g'user: rootprivileged: trueenvironment:
# sync with `executors.frontendURL` in site config
- EXECUTOR_FRONTEND_URL=http://sourcegraph-frontend-0:3080# sync with `executors.accessToken` in site config
- EXECUTOR_FRONTEND_PASSWORD=hunter2hunter2hunter2# Choose what work to process
- EXECUTOR_QUEUE_NAME=codeintel# Documenting defaults
- EXECUTOR_MAXIMUM_RUNTIME_PER_JOB=30m
- EXECUTOR_MAXIMUM_NUM_JOBS=2
- EXECUTOR_NUM_TOTAL_JOBS=200
- EXECUTOR_MAX_ACTIVE_TIME=2h# Run as root
- UID=1000
- GID=1000# Note: path must be equivalent to mounted executor-scratch (see volumes)
- TMPDIR=/tmp/sourcegraph/executor-scratchvolumes:
# Note: paths must be equivalent on host and in docker
- '/tmp/sourcegraph/executor-scratch:/tmp/sourcegraph/executor-scratch'
- '/var/run/docker.sock:/var/run/docker.sock'networks:
- sourcegraphrestart: always
Implements a portion of RFC 696: Reduced isolation deployments for executor.
Explore how to write a
docker-compose.override.yaml
file with our current executor distribution so that we can loosely bundle privileged executors on compose deployments. Findings should be added to product documentation (on installing/configuring executors).The text was updated successfully, but these errors were encountered: