fix: fallback to legacy bitnami for redis images #1704
Merged
Conversation
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
…, and fix docker compose format
ericmustin
requested review from
a team,
ahayworth,
arielvalentin,
dazuma,
fbogsany,
kaylareopelle,
mwear,
plantfansam,
robbkidd,
robertlaurin,
simi and
xuan-cao-swi
as code owners
arielvalentin
approved these changes
Sep 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Closes #1703
Workflow run: https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/18099693122/job/51499167553
The new Redis images I introduced in #1689 would require setting a password via cli, which is more complicated to configure than I had expected, and requires different configurations for both docker compose and gh workflows. It would appear for gh workflows, where we can't just modify the entrypoint script, we may have to find a different (or build/publish our own) image for redis. It requires further investigation.
I am limited on time but we can fallback to bitnamilegacy for now to unblock, which has a tradeoff of being unmaintained.