testcontainers / testcontainers/testcontainers-python
New Container: Vespa AI (Vector Database & Search Engine)
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 2.3k
- 派生
- 386
- 平均合并
- 4 小时 40 分钟
- 30 天内合并 PR
- 1
描述
What is the new container you'd like to have?
I'd like to request adding Vespa AI (the big data serving engine and vector database) container support.
- Docker container:
vespaengine/vespa:latest - Vespa website: https://vespa.ai/
- Documentation: https://docs.vespa.ai/en/vespa-quick-start.html
Benefits:
Vespa is a complete platform for building AI-powered applications with vector search, full-text search, and real-time data processing. It's particularly valuable for:
- Vector similarity search and semantic matching
- RAG (Retrieval-Augmented Generation) applications
- AI-powered search and recommendation systems
- ML model serving and inference
Having dedicated Vespa support in TestContainers would enable proper testing of modern AI applications that rely on vector databases.
Why not just use a generic container for this?
Using GenericContainer("vespaengine/vespa:latest") is not sufficient because:
Complicated setup/configuration:
- Vespa requires deploying application packages with specific configuration
- Needs multiple services (config server, container cluster) to be properly initialized
- Requires environment variables and specific startup sequence
- Application packages must be deployed and activated before the container is ready
Complex wait strategy:
- Cannot use simple HTTP wait - requires checking multiple endpoints:
- Config server health:
http://localhost:19071/state/v1/health - Container cluster readiness:
http://localhost:8080/ApplicationStatus - Configuration activation status
- Config server health:
- Startup sequence involves waiting for config server, then deploying applications, then waiting for container cluster
- Health checks need to verify multiple services are coordinated and ready
Other references:
- Vespa GitHub: https://github.com/vespa-engine/vespa
- Vespa Docker Hub: https://hub.docker.com/r/vespaengine/vespa/
- Vespa quick start guide: https://docs.vespa.ai/en/vespa-quick-start.html
- Vespa application packages: https://docs.vespa.ai/en/application-packages.html
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 Vespa 快速入门文档和 vespaengine/vespa:latest 镜像开始;梳理 config-server、container-cluster 和 application-package 的启动顺序。检查 issue 中列出的 config server 健康状态端点和 container cluster 就绪端点。当 Testcontainers Python 提供专用的 Vespa 支持,在报告就绪之前部署并激活 application package 时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- docker, python
- 领域
- databases, testing
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100