Support injecting custom config settings files via volume mount

Open
#867 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker
Domain
infrastructure

Research direction

Start with the settings location at local/core/etc/config-settings/p25/ and the quickstart container's handling of the --limits option. Verify the Docker volume mount at /config-settings/ can supply a custom settings file at runtime without rebuilding the image, and confirm the mounted file is used by the container.

Written by the indexing model from the issue text.

Description

feature request
What problem does your feature solve?

Currently, to use custom config settings (e.g., custom limits configuration), users must:

  1. Add a new settings file to the repository at local/core/etc/config-settings/p25/
  2. Build the image using one of these approaches:
    • Push to a branch and let the PR build it
    • Run make build locally
    • Create a new Docker image that inherits from stellar/quickstart and copies in the settings file (avoids rebuilding the base image)
  3. Reference the settings file via the --limits option when running the container

This workflow creates friction for users who want to quickly test with custom config settings without building custom images or forking the repository.

What would you like to see?

Support for injecting custom config settings files at runtime via a volume mount path that gets picked up automatically (e.g., /config-settings/).

This would allow users to run something like:

docker run -v ./my-settings:/config-settings stellar/quickstart --limits /config-settings/my-settings.cfg
What alternatives are there?
  • Continue with the current workflow (build custom images or fork repo)
  • Use --limits unlimited when custom limits aren't strictly necessary
  • Add a --limits-json option that accepts raw JSON text, allowing the quickstart image to write it to a file internally (no volume mount needed)
  • Inject the settings via stellar container start command, making this a feature accessed through stellar-cli rather than quickstart directly
Dominant language
Shell
Stars
222
Forks
236
Avg merge
1d 12h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/quickstart

All issues in stellar/quickstart

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.