AI / RenovateBot Interview Questions
How do you run Renovate self-hosted using Docker?
The official renovate/renovate Docker image contains the complete Renovate CLI.
# Basic Docker run for a single repository docker run --rm \ -e RENOVATE_TOKEN="${GITHUB_TOKEN}" \ renovate/renovate:latest \ --token="${GITHUB_TOKEN}" \ myorg/myrepo # With a global config file docker run --rm \ -e RENOVATE_TOKEN="${GITHUB_TOKEN}" \ -e LOG_LEVEL="debug" \ -v "$(pwd)/config.js:/usr/src/app/config.js" \ renovate/renovate:latest
// config.js â global Renovate config module.exports = { platform: "github", token: process.env.RENOVATE_TOKEN, autodiscover: true, autodiscoverFilter: ["myorg/*"], logLevel: "info", onboarding: true, extends: ["config:recommended"], prConcurrentLimit: 10, }
| Tag | Purpose |
|---|---|
| latest | Most recent stable release |
| slim | Smaller image without some infrequent managers |
| full | All managers including heavy native deps (Gradle, etc.) |
| x.y.z | Pinned specific version for reproducibility |
What is the purpose of 'autodiscover: true' in a self-hosted Renovate global config?
Which Docker image tag should you use in production for predictable, reproducible runs?
More Related questions...