integration of compose-like container groups
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
调研方向
该 issue 没有指明文件、测试或入口点。首先检查现有的容器生命周期和测试工作流，然后将其能力与 Docker Compose 对异构容器组的管理进行比较。要完成这项工作，需要就如何在测试套件中编排、运行并反复销毁多个容器系统达成一致的范围和设计。
由索引模型根据 Issue 内容生成。
描述
Although only recently having entered the containers space, I have come to understand the importance of Container Structure Test.
Docker and other developers of container infrastructure emphasize the value of building custom containers for testing general software, even software not generally targeted for containers, but few emphasize the importance of validating a container image before publishing it to external consumers.
The Docker interface is not natively friendly to the workflow of reusing an image for repeated cycles of container creation and destruction, and therefore, management of these processes is an important source of value from this project.
Automation in container testing seems to entail two critical aspects. One, as just explained, is management of the life cycle of a container and automatic processes occurring within the lifetime. The other is management of groups of containers, of heterogeneous source images, related to each other by sharing of otherwise isolated resources, such as network connectivity. Docker Compose seeks to achieve the latter objective.
In the case of robust container testing, I have come to understand, the needed for both of these automation features being integrated into a single, cogent workflow.
To make possible a truly robust test suite, a framework should allow a test suite to include specifications of any number of systems of heterogeneous containers, each such system being created and destroyed any number of times, under various specific constraints or performing various specific tasks, That is, a test suite in general should encapsulate multiple Compose-like definitions, and should handle the entire life cycle of all components from each definition.
It suggest it would be quite worthwhile for Container Structure Tests to move in such an ambitious direction.
- 主要语言
- Go
- 星标
- 2.5k
- 派生
- 213
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
GoogleContainerTools/container-structure-test 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
allstar
难度 2/5 1-3 小时 新手友好度 65/100
GoogleContainerTools/container-structure-test#393 · 639 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
GoogleContainerTools/container-structure-test#280 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 45/100
-
Windows: structure_test binary missing .exe extension causes "Open With" dialog instead of running tests可能已有人在做 @peakschris 于 146 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 72/100
查看 GoogleContainerTools/container-structure-test 的全部 Issue
相似的 Issue
-
Headerless responses block while skipping duplicate status lines可能已有人在做 @mynhe 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 73/100
projectdiscovery/rawhttp#554 ·
-
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
lognorman20/monaco#7428 ·
-
docs(prompts): IF BLOCKED workflow-scope branch says to comment on the issue on jira/local trackers未关闭agent-butler-finding bug
难度 2/5 1-3 小时 新手友好度 77/100
jordansmall/spindrift#6238 ·
维护者通常 1 天内回复