What is the new container you'd like to have?

I’d like to add Valkey, the open-source fork of Redis, as a dedicated Testcontainers module.

• Docker container: valkey/valkey:latest
• Valkey website: https://valkey.io/
• Documentation: https://valkey.io/docs/

Why not just use a generic container for this?

• Valkey adoption is growing as an alternative to Redis to avoid licensing constraints, so reliable test coverage with real Valkey instances is important.
• Valkey‑Search enables advanced features like vector search and hybrid queries with tags/filters—common in GenAI workloads. Having a container with correct modules ensures realistic integration tests.
• Valkey GLIDE provides multi-language clients (Python/Java/Node/Go) with async support and best practices; a ValkeyContainer would align with this ecosystem for integration testing.
• Parity with existing Testcontainers DB modules: Similar to RedisContainer, a dedicated ValkeyContainer simplifies setup (config, wait strategy, connection helpers) beyond what a generic container can offer.