persistent mode persists both data and code
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
Research direction
Start with the persistent mode instructions linked in the issue and inspect how the quickstart container uses /opt/stellar for data, configuration, and code. Determine a persistence layout that allows data to survive while new image code and configuration are applied, then verify that upgrading the container no longer leaves the old soroban-rpc expectation in place.
Written by the indexing model from the issue text.
Description
In the instructions for persistent mode, we tell users to mount a volume to /opt/stellar in the quickstart container.
This is problematic because that directory contains data, configuration, and code. Different versions of quickstart will have updated configuration and/or code. But, because the entire /opt/stellar directory is persisted, any changes to code and/or configuration will not be applied when running a new version of the quickstart container with the old mounted volume.
This exact situation occurred recently in https://stellarfoundation.slack.com/archives/C098N5WJCL8/p1757101644045819?thread_ts=1757078276.261149&cid=C098N5WJCL8 , where someone was running a quickstart version before soroban-rpc got renamed to stellar-rpc. The script contained within the /opt/stellar directory expected a soroban-rpc binary to be present. But the new quickstart image uses the stellar-rpc binary and no soroban-rpc binary exists.
- Dominant language
- Shell
- Stars
- 222
- Forks
- 236
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stellar/quickstart
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stellar/quickstart#932 · 16 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
stellar/quickstart#923 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stellar/quickstart#911 · 2 comments ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#907 · 1 comment ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#906 · 3 comments ·
All issues in stellar/quickstart
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·