Suggestion: Docker images should have a "manifest" detailing the configuration options required to run a container
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker
- Domain
- devops
Research direction
Start by reviewing how Docker images currently expose configuration information for ports, environment variables, and file or volume mounts, and compare that with the proposed manifest needs. Done would require an agreed manifest format and a defined implementation and validation path; this issue does not name files or tests.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 47
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/cli
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
kind/feature status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
JakeChampion/lang#10213 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100