chore: make tempo singlebinary example to use the local backend#7033
Merged
javiermolinar merged 4 commits intomainfrom Apr 22, 2026
Merged
chore: make tempo singlebinary example to use the local backend#7033javiermolinar merged 4 commits intomainfrom
javiermolinar merged 4 commits intomainfrom
Conversation
javiermolinar
requested review from
carles-grafana,
electron0zero,
ie-pham,
knylander-grafana,
mapno,
mattdurham,
mdisibio,
oleg-kozlyuk-grafana,
ruslan-mikhailov,
stoewer,
yvrhdn and
zalegrala
as code owners
Contributor
|
💻 Deploy preview deleted (chore: make tempo singlebinary example to use the local backend). |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Tempo single-binary docker-compose example to store traces on the local filesystem instead of using an S3-compatible backend (MinIO), simplifying the example stack and aligning docs with the new behavior.
Changes:
- Switch
storage.trace.backendin the single-binary example config froms3tolocaland configure the local blocks path. - Remove the MinIO service from the single-binary
docker-compose.yaml. - Update example/docs tables and the docker quickstart to no longer reference MinIO for the single-binary setup.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
example/docker-compose/single-binary/tempo.yaml |
Changes trace storage backend from S3/MinIO to local filesystem and adds local path configuration. |
example/docker-compose/single-binary/docker-compose.yaml |
Removes MinIO container and keeps the stack focused on Tempo + supporting services. |
example/docker-compose/readme.md |
Updates the examples matrix to reflect local filesystem storage for single-binary. |
docs/sources/tempo/docker-example.md |
Updates the expected docker compose ps output to remove the MinIO container entry. |
| wal: | ||
| path: /var/tempo/wal # where to store the wal locally | ||
| local: | ||
| path: /var/tempo/blocks |
Contributor
There was a problem hiding this comment.
Worth making it a named volume then - so it survives container update?
Contributor
Author
There was a problem hiding this comment.
Yes, good idea
oleg-kozlyuk-grafana
approved these changes
Apr 22, 2026
Contributor
oleg-kozlyuk-grafana
left a comment
oleg-kozlyuk-grafana
left a comment
There was a problem hiding this comment.
LGTM (pending conflict in CHANGELOG.md)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
We don't have any example using local backend. Since Tempo singlebinary can be run with a persistent volume I think its beneficial to have a simpler example
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]