testcontainers / testcontainers/testcontainers-java
[Enhancement]: Add ability to supply network to ryuk container
还没有人认领这个 Issue。
- 主要语言
- Java
- 星标
- 8.7k
- 派生
- 1.9k
- 平均合并
- 2 天 17 小时
- 30 天内合并 PR
- 9
描述
Module
Core
Synopsis
This is required due to one aspect of rootless podman networking:
https://docs.podman.io/en/latest/markdown/podman-run.1.html#network-mode-net
This implies that network is not picked up when runnig podman in rooless mode thus making it impossible for ryuk to communicate with other containers even if they were started with --network=bridge network
Proposal
Tescontainer can run using custom network (auto created via Network.createNetwork() or external) and ryuk in this case cannot be customized to use the same custom network. Some environmet can have restrictions on default network, or even have different access to each other. In this case ryuk could not see the containers at all.
Since Testcontainer already has custom env varible to override some functionality will be great to have custom varible to define:
- custom expose port for ryuk
- custom network name which ryuk container should connect during creation
Workaround in this case disable ryuk only.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先跟踪 Ryuk 容器的创建过程,以及 Core 模块中现有的环境变量覆盖机制。确认如何提供自定义网络和暴露端口,然后添加覆盖测试,验证 Ryuk 加入请求的网络并可通过配置的端口访问。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- docker, java
- 领域
- networking, testing
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100