Docker commit command appears ambiguous
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker
- Domain
- documentation
Research direction
Open the linked “Understanding image layers” documentation page and locate the “Create a base image” section and fifth step. Check the instructions around the interactive Ubuntu container, then clarify that the docker container commit command runs from the host terminal after exiting the container. Done means the step clearly distinguishes the container shell from the host terminal.
Written by the indexing model from the issue text.
Description
Is this a docs issue?
- My issue is about the documentation content or website
Type of issue
Other
Description
On 'Create a base image' section, in 5th step, the tutorial instructs users to run docker container commit -m "Add node" base-container node-base after entering an interactive Ubuntu container. As written, less-experienced users may attempt to run the command from inside the container and receive docker: command not found.
Location
https://docs.docker.com/get-started/docker-concepts/building-images/understanding-image-layers/
Suggestion
It might be helpful to explicitly state that the commit command should be executed from the host terminal after exiting the container.
No response
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 104
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/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/dhi status/triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100