FROM ... AS <name> clarification
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker
- Domain
- documentation
Research direction
Start at the Dockerfile reference page linked in the issue and locate the multi-stage build example containing COPY --from=build. Compare the named stages and references, then make the example internally explicit and verify the rendered documentation still explains the intended syntax clearly.
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
Clarification
Description
The last line of the following example snippet may confuse some beginners:
FROM ubuntu AS base
RUN apt-get update && apt-get install -y shared-tooling
FROM base AS dev
RUN apt-get install -y dev-tooling
FROM base AS prod
COPY --from=build /app /app
as there is no named build stage in the snippet. I understand that it can merely be assumed such a stage exists, but since the prod stage is built from the base base image, it takes a second to comprehend there were merely omitted steps.
Location
https://docs.docker.com/reference/dockerfile/
Suggestion
Although a bit more verbose, it would perhaps be clearer to have something along the lines of:
FROM ubuntu AS base
RUN apt-get update && apt-get install -y shared-tooling
RUN mkdir /app && touch base.txt
FROM base AS dev
RUN apt-get install -y dev-tooling
FROM base AS prod
COPY --from=base /app /app
in which everything is explicit.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 127
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Instructions no longer validPossibly taken @aevesdocker claimed this 6 days ago. Openstatus/triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
docker/docs#26171 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
letsencrypt/cp-cps#353 ·
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Docs] - Document minimum Terraform/OpenTofu version (>= 1.11) required by write-only argumentsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
MagaluCloud/terraform-provider-mgc#323 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day