stackabletech / stackabletech/docker-images
Document ways of deriving environment variables within a Dockerfile
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
As discussed in architecture meeting 04.05.2022.
Sometimes an argument is passed in to a Dockerfile which needs to be used in different forms e.g. for --build-arg PYTHON=3.8 we may need 3.8 in places (for e.g. product downloads), but 38 in others (microdnf commands). There are different ways of deriving and persisting one variable from another, and this issue covers documenting them with examples in the README e.g.
- using the moby approach of choosing a specific base image (see here)
- use an inline script wrapped by a
RUNso that the derived variable is available for the scope of that command - source the environment variables and echo the environment to a file
- etc.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the README and the linked Moby discussion on deriving values from Dockerfile build arguments. Document the listed approaches with concise examples, including their scope and persistence, and ensure the README explains how to produce both dotted and compact forms of a value such as 3.8.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100