Suggestion: Docker images should have a "manifest" detailing the configuration options required to run a container
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker
- 领域
- devops
调研方向
首先,查看 Docker images 当前如何公开 ports、environment variables 以及 file 或 volume mounts 的配置信息,并将其与拟议 manifest 的需求进行比较。完成标准是达成一致的 manifest 格式,并定义明确的实现和验证路径;此 issue 未指定文件或测试。
由索引模型根据 Issue 内容生成。
描述
Description
If you were to pick a random container from a registry, AFAIK there is currently no way to know what configuration the container needs to be run:
- Ports: You may be able to interrogate to get a list of ports, but you don't know exactly what they are for, whether they are for a common protocol or something proprietary.
- Environment variables: You don't know which need to be set, or what the values should be
- File/volume mounts: You don't know what paths will be read for configuration or volumes that need to be remapped
Why
Tools that are supposed to make working with containers easier don't have the information required to be able to prompt or guess what details need to be passed in, you have to look at the documentation. Most tools don't know how to do that, or where to find it. If that information could be packaged with the container, it would make it much easier for a variety of tools such as:
- Docker desktop UI - It could prompt for what is needed
- Hosting services could prompt and provide sensible defaults
- LLM based tools for working with compose files and kubernetes would be able to understand what each specific container needs, and be able to make more sensible options based on it.
- 主要语言
- Go
- 星标
- 6.1k
- 派生
- 2.2k
- 平均合并
- 1 天 10 小时
- 30 天内合并 PR
- 47
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
docker/cli 的其他 Issue
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 75/100
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 74/100
-
kind/feature status/0-triage
难度 2/5 1-3 小时 新手友好度 70/100
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 76/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
acceptance-tests phase-coding schema-coverage testing triaged
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100