sincecutoff.com
← all changes

BuildKitd config path accepts BUILDKITD_CONFIG

Introduced 2026-10-07 · score 0.96

HOW TO USE IT

When CI cannot inject command-line arguments, set `BUILDKITD_CONFIG` to the config file path and start `buildkitd`. An explicit `--config` flag takes precedence; if neither is set, the default path applies.

BUILDKITD_CONFIG=/etc/buildkit/custom.toml buildkitd

WHY THIS HELPS

Point BuildKitd at a custom configuration file in a restricted CI environment where injecting command-line arguments is not practical.

REQUIREMENTS AND LIMITATIONS

  • Version: v0.34.0
  • BUILDKITD_CONFIG: Environment variable containing only the configuration file path.
  • --config <path>: Selects a different configuration file path; takes precedence over BUILDKITD_CONFIG.
  • The environment variable contains only the config file path.
  • An explicit `--config` flag takes precedence over the environment variable.
  • The default path is unchanged when neither the flag nor variable is set.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card